[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

** Changed in: chromium-browser (Ubuntu) Assignee: Chad Miller (cmiller) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1250174 Title: chromium-browser

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser

Re: [Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

I don't have any way of verifying this since I don't use chromium anymore, sorry. On Wed, Apr 26, 2017 at 1:10 AM Olivier Tilloy wrote: > @James: are you still seeing this issue with recent releases of > chromium? > > -- > You received this bug notification because

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

@James: are you still seeing this issue with recent releases of chromium? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1250174 Title: chromium-browser crashed with SIGSEGV

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

** Package changed: ubuntu = chromium-browser ** Changed in: chromium-browser Importance: Unknown = Undecided -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1250174 Title:

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

** Project changed: chromium-browser = ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1250174 Title: chromium-browser crashed with SIGSEGV in

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libdrm-2.4.23 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

The zeros was definitely a fluke. The disk operations of adding to the file and updating the size was interrupted in the middle somewhere. On Tue, Dec 17, 2013 at 1:37 PM, James Mazur jamesmaz...@gmail.com wrote: I'm not having any problems with printing. I ran the bug again and this time

Re: [Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

This is probably the thread the controlling process thinks is hung. Thread 3 (Thread 0x7f82b7d36980 (LWP 4925)): #0 0x7f82badb6c67 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f82b55c62b8 in drmIoctl () from /usr/lib/x86_64-linux-gnu/libdrm.so.2

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

I'm not having any problems with printing. I ran the bug again and this time the log came up without the zeroes in it. So that might have been a fluke, because my system locked up completely as normally (no response to any keyboard / touchpad action, at all). There were also no lines from the

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

One other thing -- there is a noticeable period, a few seconds in length, after which the Google Maps screen locks up, but I can still move the mouse. I just tried having System Monitor open next to Chromium so I could see what happened to the RAM/CPU usage when Chromium froze up, but,

[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

James, when you see that happen, please log-in after it restarts and paste what is in /var/log/kern.log with time just during the crashing. ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed

Re: [Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

Thank you, James. That log is frustratingly quiet. It looks mostly normal until it is filled with zeros. It's doesn't help me much. The last line is kind of interesting. Cups, the print service, tried to do something that the security policy didn't allow. IF you're having problems with that