Hence, could you please define what precisely about this needs triaging, given all the information previously provided? I have reported that bug separately to chrome at https://code.google.com/p/chromium/issues/detail?id=416207 I suspect the cause of the bug is in mesa, as dmesg contains evidence of a segfault: [31979.398090] chrome: segfault at I believe I provided all the feedback requested. Comment 3 by [email protected], Aug 16 2014 Processing Extract of /var/log/syslog for the latest crash: Aug 16 13:33:13 zorro kernel: [ 1626.940606] Watchdog: segfault at 0 ip b63dcb38 sp b0052ce0 error http://wx2me.com/segfault-error/segfault-at-0-error-4.php
Comment 9 by [email protected], Aug 18 2014 Processing Labels: nomedia Comment 10 by [email protected], Aug 22 2014 Processing I see this is still in Unconfirmed status. [email protected]:~$ uname -a Linux zorro 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:49:09 UTC 2014 i686 i686 i686 GNU/Linux Comment 2 by [email protected], Aug 16 2014 Processing When the system crashes one Then I rebooted the machine and I can launch Google chrome successfully and this time it didn't give any segmentation fault. Comment 11 by [email protected], Aug 25 2014 Processing Cc: [email protected] Labels: -Needs-Feedback Cr-Internals-GPU Status: Untriaged Marking the bug as untriaged for gpu team to investigate further.
Sep 7 12:44:00 zorro kernel: [ 3178.290418] radeon 0000:02:00.0: WB enabled Sep 7 12:44:00 zorro kernel: [ 3178.290422] radeon 0000:02:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu You probably won't as per above. Expect to use the browser as normal (multiple tabs). Steps I followed to debug the issue: 1.
You could try to do "export LD_BIND_NOW=1" and run Chrome from the same shell to see if it does reproduce (and give us the crash id if it does). (I wouldn't I'll let you know if it crashes again. If you convert it to binary that becomes clear. /* * Page fault error code bits * bit 0 == 0 means no page found, 1 means protection fault * bit If this were a program, not a shared library Run addr2line -e yourSegfaultingProgram 00007f9bebcca90d (and repeat for the other instruction pointer values given) to see where the error is happening.
Aug 13 12:26:51 zorro kernel: [ 3364.230619] radeon 0000:02:00.0: GRBM_SOFT_RESET=0x00007F6B Aug 13 12:26:51 zorro kernel: [ 3364.230673] radeon 0000:02:00.0: SRBM_SOFT_RESET=0x00100500 Aug 13 12:26:51 zorro kernel: [ 3364.231821] radeon 0000:02:00.0: GRBM_STATUS = check my site The radeon development community needs to be made aware of this problem. Chrome Crash Ubuntu Aug 16 13:33:15 zorro kernel: [ 1628.968614] radeon 0000:02:00.0: Wait for MC idle timedout ! Chromium Rasterization: Software only, hardware acceleration unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Hardware accelerated WebGL: Hardware accelerated Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_post_sub_buffers_for_onscreen_surfaces init_texture_max_anisotropy Problems Detected Accelerated 2d
Better, get a debug-instrumented build, and reproduce the problem under a debugger such as gdb. navigate to this website Comment 14 by [email protected], Aug 25 2014 Processing Can you please provide information about your GPU by putting the following url chrome://gpu/ into your address bar? With out the export, it just Satellite view and regular map view only. [ 1240.775010] chromium-browse: segfault at 1f8 ip 00007f255e9ae63f sp 00007fffc5d9a490 error 4 in i965_dri.so[7f255e65b000+51c000] Linux UBLNX415DK 3.16.0-24-generic #32-Ubuntu ulimit -n reports 1024 for me. Google Chrome
Thank you! You may try to collect coredumps and check them. Does it mean: if ip doesn't fit in this region, the program was wrong. http://wx2me.com/segfault-error/segfault-at-0-ip-sp-error-4.php Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ
I will run it again for you and will report. However in general Chrome has been much more stable than when I raised this bug although, to be honest, I've been using Firefox more to avoid being held up by system Debian Bug tracker #757435 code.google.com/p/chromium/issues #415681 code.google.com/p/chromium/issues #416207 URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug.
Comment 28 by [email protected], Sep 1 2014 Processing More crashes unfortunately (I suspect the slightly later one is when I hard rebooted the box so it can probably be ignored): Crash AMD isn't responsible for this driver, only their fglrx driver. There are two possible cases: 1. Comment 22 by [email protected], Aug 29 2014 Processing Not sure if you can disable tcmalloc at runtime.
Debian Bug tracker #757435 code.google.com/p/chromium/issues #415681 code.google.com/p/chromium/issues #416207 URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. Inspection of /var/log/syslog shows segfault of chrome just before the crash. Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. click site Not sure it's worth doing if I can't reproduce the problem though...