Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A Page Randomly Clears Its Contents Out #94

Open
scrutinizer11 opened this issue Sep 6, 2022 · 3 comments
Open

A Page Randomly Clears Its Contents Out #94

scrutinizer11 opened this issue Sep 6, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@scrutinizer11
Copy link

scrutinizer11 commented Sep 6, 2022

Describe the bug

A page goes blank out of nowhere

To Reproduce

Steps to reproduce the behavior:

  • Go to any page

Screenshots

Screen Shot 2022-09-06 at 18 38 55
Desktop (please complete the following information):

  • OS: macOS X Lion, OS X Mavericks
  • Build 105.0.5195.52

Logs

I don't know if the log I enclose within the message contains relevant information.
65120007.txt

Add any other context about the problem here.

Several tabs are opened but I cannot state with great confidence it is related to the issue. Web-Inspector displays the blank space too with a message DevTools failed to load the source map...

@scrutinizer11 scrutinizer11 added the bug Something isn't working label Sep 6, 2022
@Wowfunhappy
Copy link

Yeah, this happens on occasion. I assume some process is crashing. To figure out why, we'd need to find a way to consistently (and precisely) reproduce the problem.

DevTools failed to load the source map...

This is unrelated. Source maps are a debugging tool for web developers who use build systems like React.

@scrutinizer11
Copy link
Author

scrutinizer11 commented Sep 11, 2022

Isn't it closer to the identifiable culprit? The loading of the page mentioned in the messages stalled.
Screen Shot 2022-09-11 at 03 41 23

@scrutinizer11
Copy link
Author

When YouTube failed to connect Console displayed this message at the time of the failure:

Chromium Helper[8061]: Failed to look up domain bootstrapper during domain extension: 0x44c

blueboxd pushed a commit that referenced this issue Sep 29, 2022
…d tab.

This CL is the follow up CL for CL:3836214. Adding tests to verify the
website metrics.

Two issues are fixed in this CL:

1. When updating the url info, not only checking the browser window's
activated statue, but also checks the tab's activated status, because
when tabs are inactivated, it could be updated as well.

2. When saving the url info to the pref, check
running_time_in_two_hours, because even if the
running_time_in_five_minutes for the tab is zero, we should still save
the url in the pref, as the UKM is recorded each 2 hours.

BUG=1355259

(cherry picked from commit 830b2e3)

Change-Id: Ia77f9f8b1ece081540df002c22b305f531918cae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3841308
Commit-Queue: Nancy Wang <nancylingwang@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1038036}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3855496
Commit-Queue: Tim Sergeant <tsergeant@chromium.org>
Reviewed-by: Tim Sergeant <tsergeant@chromium.org>
Auto-Submit: Nancy Wang <nancylingwang@chromium.org>
Cr-Commit-Position: refs/branch-heads/5249@{#94}
Cr-Branched-From: 4f7bea5-refs/heads/main@{#1036826}
blueboxd pushed a commit that referenced this issue Nov 30, 2022
UMA Blink.Layout.NGRatio.Blocks has never been count LayoutNGView as an
NG block. This CL fixes it.

After we confirm Blink.Layout.NGRatio.Blocks becomes 100% for canary,
we'll remove Blink.Layout.NGRatio.Blocks.

(cherry picked from commit ed68d65)

Bug: 1067527, 1294155, 1375906
Change-Id: I5cecab76caa715f4fbc07b743e37f017b9fbc023
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3960191
Reviewed-by: Koji Ishii <kojii@chromium.org>
Auto-Submit: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1060258}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3963155
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Auto-Submit: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/branch-heads/5359@{#94}
Cr-Branched-From: 27d3765-refs/heads/main@{#1058933}
blueboxd pushed a commit that referenced this issue Feb 8, 2023
Change-Id: Iee527ed6546a8f96703650795d21dd1b382c05d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4127524
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5481@{#94}
Cr-Branched-From: 130f3e4-refs/heads/main@{#1084008}
blueboxd pushed a commit that referenced this issue Mar 7, 2023
…ght call

When a user's device is eligible for FIDO auth and the user has at least
one server card saved, we make a preflight call when the user clicks a
payment form's field.

Currently in this preflight call we log every time we make it so that we
know the number of users that are FIDO eligible (have at least one
server card saved, and the device is FIDO eligible), though we do not
know whether the user is already opted-in to FIDO or not. This CL
expands this logging functionality to also include this detailed
information.

(cherry picked from commit 9e3d792)

Bug: 1411509
Change-Id: I632fb9708875826ac6de8e03437d23ca54a38d3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4169295
Commit-Queue: Vinny Persky <vinnypersky@google.com>
Reviewed-by: Vidhan Jain <vidhanj@google.com>
Reviewed-by: Siyu An <siyua@chromium.org>
Reviewed-by: Florian Leimgruber <fleimgruber@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1099003}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4213951
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#94}
Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
blueboxd pushed a commit that referenced this issue Apr 14, 2023
Change-Id: I6d5b893af519595b6c79697c3cc4e681d0d1d845
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4294587
Auto-Submit: Ben Mason <benmason@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5615@{#94}
Cr-Branched-From: 9c6408e-refs/heads/main@{#1109224}
blueboxd pushed a commit that referenced this issue May 9, 2023
Update custom icon dimensions 32 x 20 -> 40 x 24 on Card Unmask prompt.

Mock: https://www.figma.com/file/N6F3DN9prdEzQiylOtVBCW/X-PA-share?node-id=12465-113619&t=3FMCBR9yNh5Soqss-0
Current UI: https://hsv.googleplex.com/4739765170601984?node=15
New UI: https://hsv.googleplex.com/6070831806414848

The icon dimensions on the autofill_card_unmask_prompt_card_details
layout is changed to wrap content so it can be reused by other clients.

Note: Only custom icon dimensions are updated. Network icon dimensions
will be updated in a future change. All updates are behind
AutofillEnableNewCardArtAndNetworkImages flag.

(cherry picked from commit 33c8c9b)

Bug: 1417919, 1427674
Change-Id: I3e496bb67d0e130019a919b10846ed8fff59514d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4358991
Reviewed-by: Lijin Shen <lazzzis@google.com>
Commit-Queue: Vishwas Uppoor <vishwasuppoor@google.com>
Reviewed-by: Friedrich Horschig <fhorschig@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1122554}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4376812
Cr-Commit-Position: refs/branch-heads/5672@{#94}
Cr-Branched-From: 5f2a724-refs/heads/main@{#1121455}
blueboxd pushed a commit that referenced this issue May 27, 2023
If the user navigates to about:srcdoc or invalid URLs, the chrome
browser will crash when the SpeculativeServiceWorkerStartup feature is
enabled. This CL fixes by checking these URLs before calling
GetTentativeOriginAtRequestTime() and
StartServiceWorkerForNavigationHint().

(cherry picked from commit abb2496)

Bug: 1440062
Change-Id: I670f24c0c6847467ea370a22b2efebdf355bd4aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4478693
Commit-Queue: Minoru Chikamune <chikamune@chromium.org>
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1136874}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4493666
Auto-Submit: Minoru Chikamune <chikamune@chromium.org>
Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Commit-Queue: Charlie Reis <creis@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5735@{#94}
Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
blueboxd pushed a commit that referenced this issue Sep 10, 2023
This CL extends ReadingListEntry::IsSpecificsValid to ensure that the
entry's tilte is UTF8, which is used to validate the incoming remote
updates.

(cherry picked from commit 20c2f1b)

Fixed: 1470107
Change-Id: I347f19956c58ee50489a942f7b5848207706810d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4773579
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Mahmoud Rashad <mmrashad@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1182706}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4776058
Cr-Commit-Position: refs/branch-heads/5938@{#94}
Cr-Branched-From: 2b50cb4-refs/heads/main@{#1181205}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants