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

Chromium Helper (GPU) Crash #67

Open
pjpreilly opened this issue Jun 21, 2022 · 31 comments
Open

Chromium Helper (GPU) Crash #67

pjpreilly opened this issue Jun 21, 2022 · 31 comments
Labels
bug Something isn't working

Comments

@pjpreilly
Copy link

pjpreilly commented Jun 21, 2022

Chromium Helper (GPU) crashes while changing tabs but recovers on its own. Current Stable #819
Crash report included.....
Chromium Helper (GPU).txt

Process: Chromium Helper (GPU) [1772]
Path: /Applications/Chromium.app/Contents/Frameworks/Chromium Framework.framework/Versions/102.0.5005.115/Helpers/Chromium Helper (GPU).app/Contents/MacOS/Chromium Helper (GPU)
Identifier: Chromium Helper (GPU)
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: Chromium [1727]

Date/Time: 2022-06-21 08:03:11.204 -0400
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9

Crashed Thread: 0 CrGpuMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
objc[1772]: garbage collection is OFF

Thread 0 Crashed:: CrGpuMain Dispatch queue: com.apple.main-thread
0 org.chromium.Chromium.framework 0x00000001063cf070 viz::VizMainImpl::CreateFrameSinkManagerInternal(mojo::StructPtrviz::mojom::FrameSinkManagerParams) + 432
1 org.chromium.Chromium.framework 0x00000001063cf0d3 viz::VizMainImpl::CreateFrameSinkManager(mojo::StructPtrviz::mojom::FrameSinkManagerParams) + 67
2 org.chromium.Chromium.framework 0x00000001054c9a5f viz::mojom::VizMainStubDispatch::Accept(viz::mojom::VizMain*, mojo::Message*) + 799
3 org.chromium.Chromium.framework 0x00000001068e537c mojo::InterfaceEndpointClient::HandleIncomingMessageThunk::Accept(mojo::Message*) + 220
4 org.chromium.Chromium.framework 0x00000001068e9b77 mojo::MessageDispatcher::Accept(mojo::Message*) + 87
5 org.chromium.Chromium.framework 0x00000001068e727d mojo::InterfaceEndpointClient::HandleIncomingMessage(mojo::Message*) + 45
6 org.chromium.Chromium.framework 0x00000001068f209d mojo::internal::MultiplexRouter::Accept(mojo::Message*) + 669
7 org.chromium.Chromium.framework 0x00000001068e9b77 mojo::MessageDispatcher::Accept(mojo::Message*) + 87
8 org.chromium.Chromium.framework 0x00000001068e32d6 _ZN4base8internal7InvokerINS0_9BindStateIMN4mojo9ConnectorEFvjEJNS0_17UnretainedWrapperIS4_EEEEEFvjEE3RunEPNS0_13BindStateBaseEj + 614
9 org.chromium.Chromium.framework 0x0000000106901950 _ZN4base8internal7InvokerINS0_9BindStateIMN4mojo13SimpleWatcherEFvijRKNS3_18HandleSignalsStateEEJNS_7WeakPtrIS4_EEijS5_EEEFvvEE7RunOnceEPNS0_13BindStateBaseE + 304
10 org.chromium.Chromium.framework 0x00000001067dbdce base::TaskAnnotator::RunTaskImpl(base::PendingTask&) + 238

@pjpreilly pjpreilly added the bug Something isn't working label Jun 21, 2022
blueboxd pushed a commit that referenced this issue Jun 22, 2022
(cherry picked from commit e2ad563)

Bug: 1325425
Change-Id: I3caf2f468f9b2b2883119275a3e1c100fdac3eea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3648044
Commit-Queue: Robbie Gibson <rkgibson@google.com>
Reviewed-by: David Jean <djean@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1003913}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3652859
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5060@{#67}
Cr-Branched-From: b83393d-refs/heads/main@{#1002911}
blueboxd pushed a commit that referenced this issue Aug 31, 2022
Since this feature wants to capture new users, client-side finch
grouping is needed. This change enables the feature at 40% for
Dev/Canary/Beta

(cherry picked from commit bdf1b8d)

Bug: 1340123
Change-Id: Ibc2efab59bb9122f65926ef467d9e0e3bcfafaa8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3777766
Reviewed-by: Ginny Huang <ginnyhuang@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1028044}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3789908
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Auto-Submit: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/branch-heads/5195@{#67}
Cr-Branched-From: 7aa3f07-refs/heads/main@{#1027018}
blueboxd pushed a commit that referenced this issue Sep 29, 2022
This reverts commit 4bb4442.

Reason for revert: Memory regressions https://crbug.com/1354060

Original change's description:
> Use D3DImageBacking for more GMB formats
>
> Some shared memory GMBs, eg. software video decode, are currently using
> GLImageBacking rather than D3DImageBacking on Windows. If
> D3DImageBacking supports the GMB format then use that instead.
>
> Bug: 1293509
> Change-Id: I139e90269951519fa76aa5119da121969e9912a3
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3832932
> Commit-Queue: Kyle Charbonneau <kylechar@chromium.org>
> Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1036253}

(cherry picked from commit 9a5f5cf)

Bug: 1293509, 1354060
Change-Id: I13f24b41d32433af4dfd2864dc5f9827f2a61056
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3846023
Commit-Queue: Kyle Charbonneau <kylechar@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Original-Commit-Position: refs/heads/main@{#1037898}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3852025
Cr-Commit-Position: refs/branch-heads/5249@{#67}
Cr-Branched-From: 4f7bea5-refs/heads/main@{#1036826}
@pjpreilly
Copy link
Author

It's still an issue.....

GPU Crash Version 106.0.5249.119.txt

@Wowfunhappy
Copy link

Is there a way to reliably reproduce the crash? (I assume it doesn't happen every time you switch tabs?)

@pjpreilly
Copy link
Author

I've noticed....
Over TIME with multiple windows with one playing Sirius audio the GPU will freeze on a but not all windows occasionally .. recoverable by closing the window & reopening or opening Task Manager & killing the GPU process...upon regeneration the page comes back.

This site with uBlock Origin plays hell with the browser & always interrupts the audio on the Sirius audio tab which sometimes recovers & sometimes needs a tab reload. This scenario was happening when the GPU crashed today.

https://www.palottery.state.pa.us/#tab-1

@pjpreilly
Copy link
Author

Also as time goes by swap will grow to as large as 6GB & as swap grows the browser becomes more & more wonky......

@pjpreilly
Copy link
Author

... But no definitive steps are evident to cause this AT WILL.......

@Wowfunhappy
Copy link

Well, I'm going to leave that tab idle for a while and see if I can get memory usage to spike. If it consistently leaks memory that might be something to trace, at least.

@pjpreilly
Copy link
Author

Why don't you open 3 windows each on its own desktop with each window having 10 of those tabs... Hasten the hurt....

@pjpreilly
Copy link
Author

... And add some audio to the mix.... if you don't have Sirius add Tunein..it's free...

@pjpreilly
Copy link
Author

The Sirius audio fails with....

10/25/22 9:27:17.524 AM [0x0-0x20020].org.chromium.Chromium: [301:771:1025/092717.517014:ERROR:audio_manager_mac.cc(386)] Failed to get AudioUnit channel layout.: Error Domain=NSOSStatusErrorDomain Code=-10877 "The operation couldn’t be completed. (OSStatus error -10877.)" (-10877)

@Wowfunhappy
Copy link

Wowfunhappy commented Oct 25, 2022

That error pops up constantly all the time (including when audio is working perfectly), so I don't think that's relevant.

For whatever it's worth, I have unfortunately not been able to replicate this with those websites running over night.

@pjpreilly
Copy link
Author

I'm pretty sure it's initiated with mouse clicking activity.... what ... It's tough to say for sure...

@pjpreilly
Copy link
Author

11/4/22 10:42:31.125 AM [0x0-0x23023].org.chromium.Chromium: [289:24323:1104/104231.046341:ERROR:validation_errors.cc(117)] Invalid message: VALIDATION_ERROR_UNEXPECTED_STRUCT_HEADER

11/4/22 10:42:31.125 AM [0x0-0x23023].org.chromium.Chromium: [289:24323:1104/104231.124472:ERROR:gpu_child_thread.cc(67)] Mojo error in GPU process: Validation failed for viz.mojom.CompositorFrameSink [VALIDATION_ERROR_UNEXPECTED_STRUCT_HEADER]

11/4/22 10:42:31.136 AM [0x0-0x23023].org.chromium.Chromium: [289:24323:1104/104231.136216:ERROR:interface_endpoint_client.cc(690)] Message 2124508281 rejected by interface viz.mojom.CompositorFrameSink

11/4/22 10:43:26.675 AM [0x0-0x23023].org.chromium.Chromium: [270:1799:1104/104326.674578:ERROR:gpu_process_host.cc(971)] GPU process exited unexpectedly: exit_code=5

THEN THE GPU CRASH HAPPENS.......

@pjpreilly
Copy link
Author

pjpreilly commented Nov 4, 2022

https://bugs.chromium.org/p/chromium/issues/detail?id=1107403#:~:text=The%20attached%20zip,to%20the%20T.

Related stuff here...... comment 85...
copy link to highlight seems wonky....

@pjpreilly
Copy link
Author

viz.mojom.CompositorFrameSink error confirmed on two different machines causing a GPU crash...

@pjpreilly
Copy link
Author

@pjpreilly
Copy link
Author

pjpreilly commented Nov 4, 2022

@Wowfunhappy
Copy link

https://bugs.chromium.org/p/chromium/issues/detail?id=1107403#:~:text=The%20attached%20zip,to%20the%20T.

Related stuff here...... comment 85... copy link to highlight seems wonky....

Are you saying the test case in comment 85 triggers the crash for you?

@pjpreilly
Copy link
Author

Are you saying the test case in comment 85 triggers the crash for you?

I'm still in the investigation stage & waiting for guidance.....

@pjpreilly
Copy link
Author

pjpreilly commented Nov 4, 2022

... so no, I didn't even try it....
maybe if it breaks for you that would be helpful in investigating it further.....

UPDATE: tried it & it seems to NOT cause a crash.....

@pjpreilly
Copy link
Author

11/4/22 11:42:29.433 PM [0x0-0x35035]._Chromium: [579:20995:1104/234229.387188:FATAL:message_pump_kqueue.cc(420)] Check failed: . kevent64: Bad file descriptor (9)

11/4/22 11:43:02.163 PM [0x0-0x35035]._Chromium: [494:2823:1104/234302.162714:ERROR:gpu_process_host.cc(971)] GPU process exited unexpectedly: exit_code=5

@pjpreilly
Copy link
Author

11/4/22 10:42:31.125 AM [0x0-0x23023].org.chromium.Chromium: [289:24323:1104/104231.046341:ERROR:validation_errors.cc(117)] Invalid message: VALIDATION_ERROR_UNEXPECTED_STRUCT_HEADER

11/4/22 10:42:31.125 AM [0x0-0x23023].org.chromium.Chromium: [289:24323:1104/104231.124472:ERROR:gpu_child_thread.cc(67)] Mojo error in GPU process: Validation failed for viz.mojom.CompositorFrameSink [VALIDATION_ERROR_UNEXPECTED_STRUCT_HEADER]

11/4/22 10:42:31.136 AM [0x0-0x23023].org.chromium.Chromium: [289:24323:1104/104231.136216:ERROR:interface_endpoint_client.cc(690)] Message 2124508281 rejected by interface viz.mojom.CompositorFrameSink

11/4/22 10:43:26.675 AM [0x0-0x23023].org.chromium.Chromium: [270:1799:1104/104326.674578:ERROR:gpu_process_host.cc(971)] GPU process exited unexpectedly: exit_code=5

THEN THE GPU CRASH HAPPENS.......

11/7/22 2:21:22.819 AM [0x0-0x1d01d].org.chromium.Chromium: [273:24579:1107/022122.819238:ERROR:gpu_child_thread.cc(67)] Mojo error in GPU process: Validation failed for viz.mojom.CompositorFrameSink [VALIDATION_ERROR_UNEXPECTED_NULL_POINTER (null in array expecting valid pointers: array size - 1; index - 0)]

@pjpreilly
Copy link
Author

As of Canary version 1070008 & maybe just prior these & all Chromium crashes of unknown reproducible origin have disappeared...... I may attempt to give the the latest Stable a workout to see if it's the same there......

@pjpreilly
Copy link
Author

Crash still occurring on Stable 107.0.5304.110.2.....

blueboxd pushed a commit that referenced this issue Nov 30, 2022
Currently, if the user has already opened Chrome and never unattached or
suspended it, the color will not change even when the dark/light mode
changes. The user has to restart the app or put it on background for a
long time until the color corrects itself. This issue is fixed by this
CL.

(cherry picked from commit 9bae52d)

Fixed: 1367247
Change-Id: Ia7d934b28a23129ec22eba709f13d16eb1bc0332
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3956458
Commit-Queue: Ginny Huang <ginnyhuang@chromium.org>
Reviewed-by: Robbie Gibson <rkgibson@google.com>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Auto-Submit: Ginny Huang <ginnyhuang@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1059500}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3963732
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/branch-heads/5359@{#67}
Cr-Branched-From: 27d3765-refs/heads/main@{#1058933}
@pjpreilly
Copy link
Author

Still an issue....
Version 109.0.5414.119.1 (Official Build) (x86_64)

Chromium Helper (GPU) crash.txt
2023-01-28 09 26 07 am
2023-01-28 09 29 56 am

blueboxd pushed a commit that referenced this issue Feb 8, 2023
Change-Id: If22e96f15d5642e25c8316531d8d6ac2c699edc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4125655
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5481@{#67}
Cr-Branched-From: 130f3e4-refs/heads/main@{#1084008}
@pjpreilly
Copy link
Author

Definitely the mojo errors causing the crashes.....

@pjpreilly
Copy link
Author

2023-02-09 12 04 26 pm

@pjpreilly
Copy link
Author

org.chromium.Chromium: [289:24323:1104/104231.124472:ERROR:gpu_child_thread.cc(67)] Mojo error in GPU process: Validation failed for viz.mojom.CompositorFrameSink [VALIDATION_ERROR_UNEXPECTED_STRUCT_HEADER]

@pjpreilly
Copy link
Author

2023-02-14 07 41 15 am

These occurrences happen in the middle of the night with streaming audio playing & with no user input.

@pjpreilly
Copy link
Author

... Is anybody else seeing these GPU crashes related to mojo errors......

blueboxd pushed a commit that referenced this issue Mar 7, 2023
Incorporates changes to NTP Handler from 4183244: [ntp] Store collection ids for theme background images | https://chromium-review.googlesource.com/c/chromium/src/+/4183244 and 4193130: [ntp][side-panel] Add metric that tracks NTP image source | https://chromium-review.googlesource.com/c/chromium/src/+/4193130 to customize chrome page handler.


(cherry picked from commit 68c72f8)

Change-Id: I3af8ba3e1789e1142944d840188a91ad5fb427e0
Bug: 1384258
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4189645
Reviewed-by: Matthew Denton <mpdenton@chromium.org>
Commit-Queue: Paul Adedeji <pauladedeji@google.com>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Reviewed-by: Riley Tatum <rtatum@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1098145}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4209494
Commit-Queue: Riley Tatum <rtatum@google.com>
Reviewed-by: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/branch-heads/5563@{#67}
Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
@pjpreilly
Copy link
Author

I wonder if this is the elusive crash identified in Bug #144

blueboxd pushed a commit that referenced this issue Apr 14, 2023
(cherry picked from commit 7a22ff4)

Bug: b/270426252
Change-Id: I82d4da5c7b34ea3773af595ef81badcc74728603
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4283548
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Jiaming Cheng <jiamingc@chromium.org>
Reviewed-by: Andre Le <leandre@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1109342}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4296756
Cr-Commit-Position: refs/branch-heads/5615@{#67}
Cr-Branched-From: 9c6408e-refs/heads/main@{#1109224}
blueboxd pushed a commit that referenced this issue May 9, 2023
Uploaded by https://ci.chromium.org/b/8785423372307148417

Change-Id: I73e9679c003daae07bce87e7e5b21b69c2c5d0b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4377159
Bot-Commit: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5672@{#67}
Cr-Branched-From: 5f2a724-refs/heads/main@{#1121455}
blueboxd pushed a commit that referenced this issue May 27, 2023
- Draw top margin divider line on bottom sheet.
- Remove it when maximized to full height.
- Remove/re-draw side margins when transitioning between 900dp and regular.

(cherry picked from commit b448b1f)

Bug: 1431612
Change-Id: I00186d0581868ed399c016f75d8ad810d4c4c46a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4475141
Reviewed-by: Kevin Grosu <kgrosu@google.com>
Commit-Queue: Zach Katz <katzz@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1136059}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4483510
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5735@{#67}
Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
blueboxd pushed a commit that referenced this issue Sep 10, 2023
* Inserted missing managed dialog strings for the color picker for
  settings.
* Inserted missing default color string for the color picker for profile
  dialog.
* Rearranged the color picker strings for the profile dialog to be
  alphabetical order.

(cherry picked from commit a8e917b)

Bug: 1471315
Change-Id: I16764ff246ca70f5b6ebaf5e182f5a311991d612
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4767427
Reviewed-by: John Lee <johntlee@chromium.org>
Code-Coverage: Findit <findit-for-me@appspot.gserviceaccount.com>
Commit-Queue: Riley Tatum <rtatum@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1182223}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4775831
Cr-Commit-Position: refs/branch-heads/5938@{#67}
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