SIGTRAP

[Spr Base]

Easy to reproduce. Any devs able to investigate?

Version 84.0.4147.89 (Official Build) snap (64-bit)

Failed to open /dev/null

[0716/091926.883693:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 1 time(s)

[0716/091926.889564:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 2 time(s)

[0716/091926.893577:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 3 time(s)

[0716/091926.894491:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 4 time(s)

[0716/091926.908258:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 5 time(s)

[0716/091926.910687:WARNING:gpu_process_host.cc(1233)] The GPU process has crashed 6 time(s)

[0716/091926.910721:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.

Trace/breakpoint trap

[Jakob Kummerow]

You can file a bug at crbug.com/new.

Please include as much detail as you can: Which OS? Which GPU and driver? What does about:gpu say? How to reproduce? Does this affect Chromium, or Google Chrome, or both?

Speaking of drivers, this might well be a driver bug, so before filing a bug, try updating your drivers if you haven't already and see if that makes the issue go away. 

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

[Spr Base]

GPU is disabled on the command line.
Do you have a debug build to set a breakpoint and find why it goes
into GPU code?

https://bugs.chromium.org/p/chromium/issues/detail?id=1106509#c12

[Jakob Kummerow]

The bug is the right venue to discuss this.

I would recommend that you try to have a constructive conversation with the people who have been trying to help you there, such as answering their questions.

(This may be obvious, but if you refuse to answer someone's questions and instead tell that person that they are incompetent, then chances are others don't want to spend their time on this issue at all, and you might just get an answer along the lines of "Chromium is open source, go fix it yourself", which probably isn't what you were hoping for. If you want help, be cooperative.)

[Spr Base]

Thanks for the advice!

Yesterday I provided the steps to reproduce this crash on the bug. It
shouldn't get to any GPU host code.. as GPU is disabled on command
line..?

I've attached another easy to reproduce chrome crash test case. It
runs it on the command line, you'll need to compile with g++ the test
case, or adapt it to launch a shell script or python etc.

Cheers

[Spr Base]

Forgot to ask, is there a good debug build with symbols available as a deb?
I compiled from source, for 18 hours, but it doesn't run. the ASAN
build I downloaded doesn't run on Ubuntu LTS.... ran out of options.