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.

Sign up for GitHub

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

Jump to bottom

Renderer [CRASH] on latest Canary 102.0.5000.0 #58

Closed
pjpreilly opened this issue Apr 13, 2022 · 12 comments
Closed

Renderer [CRASH] on latest Canary 102.0.5000.0 #58

pjpreilly opened this issue Apr 13, 2022 · 12 comments
Labels
bug Something isn't working

Comments

@pjpreilly
Copy link

pjpreilly commented Apr 13, 2022 •
edited
Loading

I have 3 pages with multiple tabs
The renderer has stopped on 2 desktops while one still works
I can recover page operation by opening Task Manager & killing the GPU process it then restarts
When I change tabs the title bar gets updated but the correct tab is not rendered

The mechanism to reproduce is unknown

osx Lion
version 102.0.5000.0 Build [991524]

chromium renderer crash 4-13.zip
@pjpreilly pjpreilly added the bug Something isn't working label Apr 13, 2022
@pjpreilly
Copy link
Author

Note: one tab is streaming Sirius audio....fwiw

@blueboxd
Copy link
Owner

Hmm, seems crashed in V8, and crashed function got recently changed.
Maybe not a bug of -legacy.
Please take a look a while at the latest builds.

@pjpreilly
Copy link
Author

The renderer has stopped on 2 desktops while one still works
I can recover page operation by opening Task Manager & killing the GPU process it then restarts
When I change tabs the title bar gets updated but the correct tab is not rendered

Still seeing this on latest canary....

@Wowfunhappy
Copy link

I generally don't pay attention to random crashes like this unless they're happening in a stable build. Official Chrome crashes all the time in Canary builds, it probably doesn't have anything to do with Chromium Legacy.

@pjpreilly
Copy link
Author

It doesn't crash...... the page doesn't update until I kill the gpu process....
The title of the page changes when I change tabs but the tab that is displayed is frozen....

@Wowfunhappy
Copy link

Okay, well what I said applies to hangs too. 🤷‍♂️

@pjpreilly
Copy link
Author

Okay, well what I said applies to hangs too. 🤷‍♂️

Switched to stable & hangs persit where I have to end the GPU process to continue.
No process crashes though......

@Wowfunhappy
Copy link

🙁

Have you managed to find a way to reproduce the crash, or does it seem to be completely random?

@pjpreilly
Copy link
Author

🙁

Have you managed to find a way to reproduce the crash, or does it seem to be completely random?

Just switching tabs & windows while Sirius radio streams audio ... gpu processing usually only freezes on one window.
I'll switch to a different tab & only the title bar updates, pointer is active & seems to be clickable on the non updated window.
4GB memory & swap tends to keep climbing sometimes as high as 6 or 7 GB with millions of swap ins & outs....

@pjpreilly
Copy link
Author

& fwiw this page tends to load really slow & will cause the streaming audio to hiccup...
https://www.palottery.state.pa.us/#tab-1

It loads fine on cloudready 96.4.36 on the same hardware......

@pjpreilly
Copy link
Author

pjpreilly commented Apr 25, 2022 •
edited
Loading

This flag enabled seems to help the lottery page more than disable...

Increase the nesting threshold before which setTimeout(..., <4ms) start being clamped.
setTimeout(..., 0) is commonly used to break down long Javascript tasks. Under this flag, setTimeouts and setIntervals with an interval < 4ms are not clamped as aggressively. This improves short horizon performance, but websites abusing the API will still eventually have their setTimeouts clamped. – Mac, Windows, Linux, ChromeOS, Android, Fuchsia, Lacros

#unthrottled-nested-timeout

but its only available on canary & not stable...

@blueboxd
Copy link
Owner

I close for now.
Please re-open if issue persists.

blueboxd pushed a commit that referenced this issue Jun 22, 2022
[M103] [infra] Migrate configs for Cast Linux Debug src-side
3b1bb31 
(cherry picked from commit c285a69)

Bug: 1317122
Change-Id: I58e65c5e5766511af441409fc7dac1106bb14ac6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3645340
Commit-Queue: Garrett Beaty <[email protected]>
Reviewed-by: Garrett Beaty <[email protected]>
Auto-Submit: Wanda Mora <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1004480}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3652691
Commit-Queue: Rubber Stamper <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5060@{#58}
Cr-Branched-From: b83393d-refs/heads/main@{#1002911}
blueboxd pushed a commit that referenced this issue Aug 31, 2022
[Journeys] Fix position of optout menu item
cf9a3d0 
Its visibility won't be controlled properly unless it's in the "normal"
group.

(cherry picked from commit 481cc63)

Bug: 1303171, 1346697
Change-Id: I3eb9134f3367ef63a602b6e9a7d7b68c71695521
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3781007
Reviewed-by: Ted Choc <[email protected]>
Reviewed-by: Gang Wu <[email protected]>
Commit-Queue: Patrick Noland <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1027867}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3788396
Reviewed-by: Krishna Govind <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Commit-Queue: Krishna Govind <[email protected]>
Owners-Override: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/5195@{#58}
Cr-Branched-From: 7aa3f07-refs/heads/main@{#1027018}
blueboxd pushed a commit that referenced this issue Sep 29, 2022
[Merge to 106][RDSD] Add feature engagement for the RDS app menu setting
0100f03 
(cherry picked from commit 176d559)

Bug: 1353597
Change-Id: I43b96d830ff4e31144e0cc5f94c7395d1e2c4ccd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3840402
Reviewed-by: Shu Yang <[email protected]>
Commit-Queue: Aishwarya Rajesh <[email protected]>
Reviewed-by: Theresa Sullivan <[email protected]>
Reviewed-by: Alexei Svitkine <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1037825}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3852961
Reviewed-by: Weilun Shi <[email protected]>
Cr-Commit-Position: refs/branch-heads/5249@{#58}
Cr-Branched-From: 4f7bea5-refs/heads/main@{#1036826}
blueboxd pushed a commit that referenced this issue Nov 30, 2022
Added controller for reader mode CPA
ee9dc0a 
This CL adds a button controller for reader mode as a contextual page
actions.

(cherry picked from commit acad206)

Bug: 1373898
Change-Id: I35aaa9fa719d333a7dcdad303211ef0d4b8a409b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3940208
Reviewed-by: Tommy Nyquist <[email protected]>
Reviewed-by: Shakti Sahu <[email protected]>
Commit-Queue: Salvador Guerrero Ramos <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1059371}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3962429
Cr-Commit-Position: refs/branch-heads/5359@{#58}
Cr-Branched-From: 27d3765-refs/heads/main@{#1058933}
blueboxd pushed a commit that referenced this issue Feb 8, 2023
[UPM] Add new strings for the save/update password prompts
37af202 
New strings will be used to analyse the effect of new branding on
the password save acceptance rate. There are two variants to be
checked, exact version to be used is determined by the finch config.

These changes are under the feature flag and should not affect the
default behaviour.

(cherry picked from commit 616dddf)

Bug: 1402280
Change-Id: Id1a0e999b89133703c888a98baefaa6cd80f512d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4111558
Reviewed-by: Mohamed Amir Yosef <[email protected]>
Commit-Queue: Maxim Anufriev <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1086431}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4123137
Commit-Queue: Mohamed Amir Yosef <[email protected]>
Auto-Submit: Maxim Anufriev <[email protected]>
Cr-Commit-Position: refs/branch-heads/5481@{#58}
Cr-Branched-From: 130f3e4-refs/heads/main@{#1084008}
blueboxd pushed a commit that referenced this issue Mar 7, 2023
@liberato-at-chromium
[M111] Turn off desktop media capture from Document Picture in Picture
31132ca 
Since the UI around media capture doesn't work with the always-on-
top picture in picture window, and since it's likely that it's not
something we want to support anyway, turn it off for origin trial.

(cherry picked from commit f69e1d2)

Bug: 1410382
Change-Id: If86abad9ace8a38008f91eb48dca0abd54637aef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4195679
Reviewed-by: John Rummell <[email protected]>
Commit-Queue: Frank Liberato <[email protected]>
Reviewed-by: Elad Alon <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1097633}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4209808
Auto-Submit: Frank Liberato <[email protected]>
Commit-Queue: Rubber Stamper <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#58}
Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
blueboxd pushed a commit that referenced this issue Apr 14, 2023
Roll ChromeOS Bigcore AFDO profile from 112-5563.14-1676891310-benchm…
dc5a347 
…ark-112.0.5615.6-r1 to 112-5594.0-1677500680-benchmark-112.0.5615.8-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-bigcore-chromium-beta
Please CC [email protected] on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: [email protected]
Change-Id: I6e6261b85cadd426f10b64bb593b8fd6bbd1db08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4296192
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5615@{#58}
Cr-Branched-From: 9c6408e-refs/heads/main@{#1109224}
blueboxd pushed a commit that referenced this issue May 9, 2023
@khushalsagar
Revert "view-transitions: Don't damage full surface during transitions."
1ce8d6f 
This reverts commit 05671df.

Reason for revert: There are multiple issues pertaining damage that have likely been masked by the logic being removed here. Fixes for those should happen first.

Bug: 1427721
Original change's description:
> view-transitions: Don't damage full surface during transitions.
>
> If the frame for a Surface was replaced by SurfaceAnimationManager, the
> code assumes the whole surface needs to be damaged. This was needed when
> the animation was viz driven, that code didn't compute the damage rect.
> But now that its all driven in the renderer, CC should be setting up
> the damage rects correctly.
>
> R=​[email protected], [email protected]
>
> Change-Id: I4e5053237c9533faef16b78874fa66e06f7542df
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4367538
> Commit-Queue: Maggie Chen <[email protected]>
> Auto-Submit: Khushal Sagar <[email protected]>
> Reviewed-by: Maggie Chen <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1121404}

(cherry picked from commit 5f3104b)

Change-Id: I4c2143bfe4e2b2a45d093923d8f03c189acbf168
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4368788
Bot-Commit: Rubber Stamper <[email protected]>
Commit-Queue: Khushal Sagar <[email protected]>
Reviewed-by: Maggie Chen <[email protected]>
Reviewed-by: Khushal Sagar <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1122048}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4375297
Reviewed-by: Vladimir Levin <[email protected]>
Commit-Queue: Vladimir Levin <[email protected]>
Auto-Submit: Khushal Sagar <[email protected]>
Commit-Queue: Maggie Chen <[email protected]>
Cr-Commit-Position: refs/branch-heads/5672@{#58}
Cr-Branched-From: 5f2a724-refs/heads/main@{#1121455}
blueboxd pushed a commit that referenced this issue May 27, 2023
[Synced MVTs] Create local-state int Pref for Synced MVTs.
65328fc 
This change prevents foreign history from being included in segments
data when the following conditions are met:

1. The New Tab Page (on iOS) has been displayed, at least, 5 times.
2. The app is being launched freshly.

From this point on, foreign history will not be included in segments
data.

(cherry picked from commit e8aaed2)

Change-Id: Ic54bb0bd58e1f9b56cbc54949eae6cfd29c66afd
Bug: 1431954
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4324438
Commit-Queue: Benjamin Williams <[email protected]>
Code-Coverage: Findit <[email protected]>
Reviewed-by: Scott Violet <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1135990}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4479997
Reviewed-by: Rohit Rao <[email protected]>
Cr-Commit-Position: refs/branch-heads/5735@{#58}
Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
blueboxd pushed a commit that referenced this issue May 16, 2024
@snianu
Revert "[Clipboard] Don't add meta charset tag for async write() meth…
5814366 
…od on Mac."

This reverts commit 0a05892.

Reason for revert: Caused regressions during copy. crbug.com/333989067.

Original change's description:
> [Clipboard] Don't add meta charset tag for async write() method on Mac.
>
> Remove the logic from the browser process that prepends a meta
> charset tag to the HTML markup before writing to the pasteboard.
> Instead, add the meta charset tag only for copy/paste commands in the
> Blink code.
>
> Bug: 1504501
>
> Change-Id: I95ec6e2dc6395076af78bfbbba78b8579ff16857
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5187335
> Reviewed-by: Avi Drissman <[email protected]>
> Reviewed-by: Koji Ishii <[email protected]>
> Commit-Queue: Anupam Snigdha <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1257511}

(cherry picked from commit 7bf0ba4)

(cherry picked from commit ebdb716)

Bug: 1504501, 333989067
Change-Id: I703e2dcd3c5bd8d2ef6a3da44ce17a7e25218d96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5455853
Reviewed-by: Avi Drissman <[email protected]>
Commit-Queue: Anupam Snigdha <[email protected]>
Reviewed-by: Koji Ishii <[email protected]>
Cr-Original-Original-Commit-Position: refs/heads/main@{#1288202}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5463860
Commit-Queue: Koji Ishii <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Auto-Submit: Anupam Snigdha <[email protected]>
Cr-Original-Commit-Position: refs/branch-heads/6422@{#58}
Cr-Original-Branched-From: 9012208-refs/heads/main@{#1287751}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5464132
Reviewed-by: Daniel Yip <[email protected]>
Owners-Override: Daniel Yip <[email protected]>
Reviewed-by: Christine Hollingsworth <[email protected]>
Cr-Commit-Position: refs/branch-heads/6367@{#916}
Cr-Branched-From: d158c6d-refs/heads/main@{#1274542}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Wowfunhappy @pjpreilly @blueboxd