chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

StacktraceTop:
 content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang (this=<optimized out>) at content/gpu/gpu_watchdog_thread.cc:230
 Run (this=0x7f82b764e8d8) at ./base/callback.h:396
 base::MessageLoop::RunTask (this=0x7f82b764ea80, pending_task=...) at base/message_loop/message_loop.cc:482
 base::MessageLoop::DeferOrRunPendingTask (this=0x7f82b764ea80, pending_task=...) at base/message_loop/message_loop.cc:494
 DoDelayedWork (next_delayed_work_time=0x7f82b0000a98, this=0x7f82b764ea80) at base/message_loop/message_loop.cc:646

James, please paste what "about:gpu" says.

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Compositing: Hardware accelerated
3D CSS: Hardware accelerated
CSS Animation: Accelerated
WebGL: Hardware accelerated
WebGL multisampling: Hardware accelerated
Flash 3D: Hardware accelerated
Flash Stage3D: Unavailable. Hardware acceleration unavailable
Flash Stage3D Baseline profile: Unavailable. Hardware acceleration unavailable
Texture Sharing: Hardware accelerated
Video Decode: Software only, hardware acceleration unavailable
Video: Hardware accelerated
Problems Detected
Accelerated 2d canvas is unstable in Linux at the moment.
Stage3D is not supported on Linux.: 129848
Accelerated video decode is unavailable on Mac and Linux.: 137247, 133828
Force compositing mode is off, either disabled at the command line or not supported by the current system.
Driver Bug Workarounds
clear_alpha_in_readpixels
disable_ext_occlusion_query
set_texture_filter_before_generating_mipmap
Version Information
Data exported 11/18/2013 4:57:27 PM
Chrome version Chrome/30.0.1599.114
Operating system Linux 3.8.0-33-generic
Software rendering list version 6.5
Driver bug list version 2.6
ANGLE revision 2431
2D graphics backend Skia
Driver Information
Initialization time 92
Sandboxed true
GPU0 VENDOR = 0x8086, DEVICE= 0x0106
Optimus false
AMD switchable false
Driver vendor Mesa
Driver version 9.1.7
Driver date
Pixel shader version 1.30
Vertex shader version 1.30
Machine model
GL version 3.0
GL_VENDOR Intel Open Source Technology Center
GL_RENDERER Mesa DRI Intel(R) Sandybridge Mobile
GL_VERSION 3.0 Mesa 9.1.7
GL_EXTENSIONS GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_texture GL_EXT_polygon_offset GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_3DFX_texture_compression_FXT1 GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_ATI_envmap_bumpmap GL_EXT_stencil_two_side GL...

James, does the proposed chromium in this PPA behave better?

https://launchpad.net/~canonical-chromium-builds/+archive/stage

Yes. Oddly enough, before installing the PPA, I tried from the same
version of Chromium as when the bug occurred, and Google Maps was working
again. So I don't think it was necessarily a problem with Chromium. I
tried it with the version from the PPA, too; Google Maps was also working
on there.

On Wed, Nov 20, 2013 at 10:26 AM, Chad Miller <email address hidden>wrote:

> James, does the proposed chromium in this PPA behave better?
>
> https://launchpad.net/~canonical-chromium-builds/+archive/stage
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1250174
>
> Title:
> chromium-browser crashed with SIGSEGV in
> content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()
>
> Status in Chromium Browser:
> Unknown
> Status in “chromium-browser” package in Ubuntu:
> Incomplete
>
> Bug description:
> I was using Google Maps and Chromium froze up and crashed. After
> this, rendering of the new Google Maps page causes jagged lines to
> appear in the browser page display section, until I reboot the
> computer. Killing and relaunching Chromium doesn't fix the problem.
> The jagged lines still appear after computer reboot if I visit Google
> Maps again, and again won't disappear until I restart the computer.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: chromium-browser 30.0.1599.114-0ubuntu0.12.04.3
> ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
> Uname: Linux 3.8.0-33-generic x86_64
> ApportVersion: 2.0.1-0ubuntu17.6
> Architecture: amd64
> ChromiumPrefs: can't open profile
> /home/jamesmaz/.config/chromium/Default/Preferences
> Date: Mon Nov 11 13:10:09 2013
> Desktop-Session:
> DESKTOP_SESSION = ubuntu
> XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
> XDG_DATA_DIRS =
> /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
> Env:
> MOZ_PLUGIN_PATH = None
> LD_LIBRARY_PATH = None
> ExecutablePath: /usr/lib/chromium-browser/chromium-browser
> InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
> (20130820.1)
> MarkForUpload: True
> ProcCmdline: /usr/lib/chromium-browser/chromium-browser\
> --type=gpu-process\ --channel=4656.10.459810737\
> --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=0,6,18\
> --gpu-vendor-id=0x8086\ --gpu-device-id=0x0106\ --gpu-driver-vendor=Mesa\
> --gpu-driver-version=9.1.7
> ProcEnviron:
>
> SegvAnalysis:
> Segfault happened at: 0x7f82c62ad43e: movl $0x1337,0x0
> PC (0x7f82c62ad43e) ok
> source "$0x1337" ok
> destination "0x0" (0x00000000) not located in a known VMA region
> (needed writable region)!
> Stack memory exhausted (SP below stack segment)
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: chromium-browser
> StacktraceTop:
> ?? () from /usr/lib/chromium-browser/libs/libcontent.so
> base::MessageLoop::RunTask(base::PendingTask const&) () from
> /usr/lib/chromium-browser/libs/libbase.so
> base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) ()
> from /usr/lib/chromium-browser/libs/libbase.so
> base::MessageLoo...

Chromium still seems to be having problems with the Google Maps site. Now my entire system locks up when I do a search; I have to hold down the power button on my laptop to turn it off. I'm in "Version 31.0.1650.57 Ubuntu 12.04 (31.0.1650.57-0ubuntu0.12.04.1~cm1precise1)" of Chromium right now.

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.

Hopefully this contains the info you need:

Dec 16 13:01:26 jamesmaz-K54C kernel: [ 8813.173174] cfg80211: Calling CRDA to update world regulatory domain
Dec 16 13:01:28 jamesmaz-K54C kernel: [ 8814.368961] wlan0: authenticate with b4:e9:b0:ee:46:71
Dec 16 13:01:28 jamesmaz-K54C kernel: [ 8814.383892] wlan0: send auth to b4:e9:b0:ee:46:71 (try 1/3)
Dec 16 13:01:28 jamesmaz-K54C kernel: [ 8814.393485] wlan0: authenticated
Dec 16 13:01:28 jamesmaz-K54C kernel: [ 8814.395364] wlan0: associate with b4:e9:b0:ee:46:71 (try 1/3)
Dec 16 13:01:28 jamesmaz-K54C kernel: [ 8814.599200] wlan0: associate with b4:e9:b0:ee:46:71 (try 2/3)
Dec 16 13:01:28 jamesmaz-K54C kernel: [ 8814.802919] wlan0: associate with b4:e9:b0:ee:46:71 (try 3/3)
Dec 16 13:01:28 jamesmaz-K54C kernel: [ 8815.006716] wlan0: association with b4:e9:b0:ee:46:71 timed out
Dec 16 13:01:29 jamesmaz-K54C kernel: [ 8816.214932] wlan0: authenticate with 04:da:d2:b3:cd:71
Dec 16 13:01:29 jamesmaz-K54C kernel: [ 8816.230030] wlan0: send auth to 04:da:d2:b3:cd:71 (try 1/3)
Dec 16 13:01:29 jamesmaz-K54C kernel: [ 8816.231865] wlan0: authenticated
Dec 16 13:01:29 jamesmaz-K54C kernel: [ 8816.233770] wlan0: associate with 04:da:d2:b3:cd:71 (try 1/3)
Dec 16 13:01:30 jamesmaz-K54C kernel: [ 8816.257754] wlan0: RX AssocResp from 04:da:d2:b3:cd:71 (capab=0x431 status=0 aid=1)
Dec 16 13:01:30 jamesmaz-K54C kernel: [ 8816.257865] wlan0: associated
Dec 16 13:01:33 jamesmaz-K54C kernel: [ 8819.388079] wlan0: deauthenticated from 04:da:d2:b3:cd:71 (Reason: 15)
Dec 16 13:01:33 jamesmaz-K54C kernel: [ 8819.398579] cfg80211: Calling CRDA for country: US
Dec 16 13:01:34 jamesmaz-K54C kernel: [ 8820.598149] wlan0: authenticate with 04:da:d2:b3:eb:31
Dec 16 13:01:34 jamesmaz-K54C kernel: [ 8820.613160] wlan0: send auth to 04:da:d2:b3:eb:31 (try 1/3)
Dec 16 13:01:34 jamesmaz-K54C kernel: [ 8820.614125] wlan0: authenticated
Dec 16 13:01:34 jamesmaz-K54C kernel: [ 8820.616859] wlan0: associate with 04:da:d2:b3:eb:31 (try 1/3)
Dec 16 13:01:34 jamesmaz-K54C kernel: [ 8820.630862] wlan0: RX AssocResp from 04:da:d2:b3:eb:31 (capab=0x431 status=0 aid=50)
Dec 16 13:01:34 jamesmaz-K54C kernel: [ 8820.630937] wlan0: associated
Dec 16 13:02:06 jamesmaz-K54C kernel: [ 8852.837326] wlan0: authenticate with 04:da:d2:b3:e0:81
Dec 16 13:02:06 jamesmaz-K54C kernel: [ 8852.845791] wlan0: send auth to 04:da:d2:b3:e0:81 (try 1/3)
Dec 16 13:02:06 jamesmaz-K54C kernel: [ 8852.846094] cfg80211: Calling CRDA to update world regulatory domain
Dec 16 13:02:06 jamesmaz-K54C kernel: [ 8852.855072] wlan0: authenticated
Dec 16 13:02:06 jamesmaz-K54C kernel: [ 8852.857203] wlan0: associate with 04:da:d2:b3:e0:81 (try 1/3)
Dec 16 13:02:06 jamesmaz-K54C kernel: [ 8852.895968] wlan0: RX AssocResp from 04:da:d2:b3:e0:81 (capab=0x431 status=0 aid=104)
Dec 16 13:02:06 jamesmaz-K54C kernel: [ 8852.896070] wlan0: associated
Dec 16 13:02:31 jamesmaz-K54C kernel: [ 8877.271003] cfg80211: Calling CRDA for country: US
Dec 16 13:02:31 jamesmaz-K54C kernel: [ 8877.490499] wlan0: authenticate with 04:da:d2:b3:eb:31
Dec 16 13:02:31 jamesmaz-K54C kernel: [ 8877.506428] wlan0: send auth to 04:da:d2:b3:eb:31 (try 1/3)
Dec 16 13:02:31 jamesmaz-K54C kernel: [ 8877....

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 too, you might file a bug and attach that. I'd title it "cups
apparmor profile denied 'block_suspend' capability".

Dec 16 13:03:43 jamesmaz-K54C kernel: [ 8949.398708] type=1400
> audit(1387217023.287:29): apparmor="DENIED" operation="capable" parent=1
> profile="/usr/sbin/cupsd" pid=891 comm="cupsd" pid=891 comm="cupsd"
> capability=36 capname="block_suspend"
>
> \00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
>

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 past 10 minutes before the crash, which would have included when I first started Chromium and when I first visited the Google Maps page.

I also played music in the background to see what would happen...it turned out that the same half-second of the song kept being repeated over and over again...it sounded like a broken record, or a skip in a CD. Maybe the fact that the music didn't just stop gives a clue?

Finally, I figured out what in particular seems to cause the lockup. It is not just visiting Google Maps, or even just panning and zooming after doing a search. It's, weird as it sounds, zooming out after having been zoomed in very close.

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, interestingly enough, the System Monitor line graph froze up at the exact same time as the Google Maps screen, even during the period in which I could move the mouse. BUT the music I was playing in the background continued normally in the few seconds I could move the mouse. So perhaps it is something with drawing that is causing the crash? Though it would have to be pretty general, as re-drawing in both System Monitor and Chromium froze up. Yet not so general that it stops the cursor from being redrawn.

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 <email address hidden> wrote:

> 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 past 10 minutes before the
> crash, which would have included when I first started Chromium and when
> I first visited the Google Maps page.
>
> I also played music in the background to see what would happen...it
> turned out that the same half-second of the song kept being repeated
> over and over again...it sounded like a broken record, or a skip in a
> CD. Maybe the fact that the music didn't just stop gives a clue?
>
> Finally, I figured out what in particular seems to cause the lockup. It
> is not just visiting Google Maps, or even just panning and zooming after
> doing a search. It's, weird as it sounds, zooming out after having been
> zoomed in very close.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1250174
>
> Title:
> chromium-browser crashed with SIGSEGV in
> content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()
>
> Status in Chromium Browser:
> Unknown
> Status in “chromium-browser” package in Ubuntu:
> Incomplete
>
> Bug description:
> I was using Google Maps and Chromium froze up and crashed. After
> this, rendering of the new Google Maps page causes jagged lines to
> appear in the browser page display section, until I reboot the
> computer. Killing and relaunching Chromium doesn't fix the problem.
> The jagged lines still appear after computer reboot if I visit Google
> Maps again, and again won't disappear until I restart the computer.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: chromium-browser 30.0.1599.114-0ubuntu0.12.04.3
> ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
> Uname: Linux 3.8.0-33-generic x86_64
> ApportVersion: 2.0.1-0ubuntu17.6
> Architecture: amd64
> ChromiumPrefs: can't open profile
> /home/jamesmaz/.config/chromium/Default/Preferences
> Date: Mon Nov 11 13:10:09 2013
> Desktop-Session:
> DESKTOP_SESSION = ubuntu
> XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
> XDG_DATA_DIRS =
> /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
> Env:
> MOZ_PLUGIN_PATH = None
> LD_LIBRARY_PATH = None
> ExecutablePath: /usr/lib/chromium-browser/chromium-browser
> InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
> (20130820.1)
> MarkForUpload: True
> ProcCmdline: /usr/lib/chromium-browser/chromium-browser\
> --type=gpu-process\ --channel=4656.10.459810737\
> --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=0,6,18\
> --gpu-vendor-id=0x8086\ --gpu-device-id=0x0106\ --gpu-driver-vendor=Mesa\
> --gpu-driver-version=9.1.7
> ProcEnviron:
>
> SegvAnalysis:
> Segfault happ...

This is probably the thread the controlling process thinks is hung.

Thread 3 (Thread 0x7f82b7d36980 (LWP 4925)):
#0 0x00007f82badb6c67 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1 0x00007f82b55c62b8 in drmIoctl () from
/usr/lib/x86_64-linux-gnu/libdrm.so.2
No symbol table info available.
#2 0x00007f82b4b1049f in drm_intel_gem_bo_start_gtt_access () from
/usr/lib/x86_64-linux-gnu/libdrm_intel.so.1
No symbol table info available.
#3 0x00007f82b531164a in ?? () from
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
No symbol table info available.
#4 0x00007f82b5312671 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
No symbol table info available.
#5 0x00007f82b5399baf in ?? () from
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
No symbol table info available.
#6 0x00007f82b6259d7f in ?? () from
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
No symbol table info available.
#7 0x00007f82b6231563 in glXMakeCurrentReadSGI () from
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
No symbol table info available.
#8 0x00007f82c4a13894 in ?? () from
/usr/lib/chromium-browser/libs/libgl_wrapper.so
No symbol table info available.
#9 0x00007f82c6b5d4e7 in ?? () from
/usr/lib/chromium-browser/libs/libgpu.so
No symbol table info available.
#10 0x00007f82c6271503 in ?? () from
/usr/lib/chromium-browser/libs/libcontent.so

On Tue, Dec 17, 2013 at 1:57 PM, Chad Miller <email address hidden>wrote:

> 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 <email address hidden>wrote:
>
>> 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 past 10 minutes before the
>> crash, which would have included when I first started Chromium and when
>> I first visited the Google Maps page.
>>
>> I also played music in the background to see what would happen...it
>> turned out that the same half-second of the song kept being repeated
>> over and over again...it sounded like a broken record, or a skip in a
>> CD. Maybe the fact that the music didn't just stop gives a clue?
>>
>> Finally, I figured out what in particular seems to cause the lockup. It
>> is not just visiting Google Maps, or even just panning and zooming after
>> doing a search. It's, weird as it sounds, zooming out after having been
>> zoomed in very close.
>>
>> --
>> You received this bug notification because you are a bug assignee.
>> https://bugs.launchpad.net/bugs/1250174
>>
>> Title:
>> chromium-browser crashed with SIGSEGV in
>> content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()
>>
>> Status in Chromium Browser:
>> Unknown
>> Status in “chromium-browser” package in Ubuntu:
>> Incomplete
>>
>> Bug description:
>> I was using Google Maps and Chromium froze up and crashed. After
>> this, rendering of the new Google Maps page causes jagged li...

Status changed to 'Confirmed' because the bug affects multiple users.

@James: are you still seeing this issue with recent releases of chromium?

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 <email address hidden>
wrote:

> @James: are you still seeing this issue with recent releases of
> chromium?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1250174
>
> Title:
> chromium-browser crashed with SIGSEGV in
> content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()
>
> Status in Chromium Browser:
> Unknown
> Status in chromium-browser package in Ubuntu:
> Incomplete
> Status in libdrm-2.4.23 package in Ubuntu:
> Confirmed
>
> Bug description:
> I was using Google Maps and Chromium froze up and crashed. After
> this, rendering of the new Google Maps page causes jagged lines to
> appear in the browser page display section, until I reboot the
> computer. Killing and relaunching Chromium doesn't fix the problem.
> The jagged lines still appear after computer reboot if I visit Google
> Maps again, and again won't disappear until I restart the computer.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: chromium-browser 30.0.1599.114-0ubuntu0.12.04.3
> ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
> Uname: Linux 3.8.0-33-generic x86_64
> ApportVersion: 2.0.1-0ubuntu17.6
> Architecture: amd64
> ChromiumPrefs: can't open profile
> /home/jamesmaz/.config/chromium/Default/Preferences
> Date: Mon Nov 11 13:10:09 2013
> Desktop-Session:
> DESKTOP_SESSION = ubuntu
> XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
> XDG_DATA_DIRS =
> /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
> Env:
> MOZ_PLUGIN_PATH = None
> LD_LIBRARY_PATH = None
> ExecutablePath: /usr/lib/chromium-browser/chromium-browser
> InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
> (20130820.1)
> MarkForUpload: True
> ProcCmdline: /usr/lib/chromium-browser/chromium-browser\
> --type=gpu-process\ --channel=4656.10.459810737\
> --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=0,6,18\
> --gpu-vendor-id=0x8086\ --gpu-device-id=0x0106\ --gpu-driver-vendor=Mesa\
> --gpu-driver-version=9.1.7
> ProcEnviron:
>
> SegvAnalysis:
> Segfault happened at: 0x7f82c62ad43e: movl $0x1337,0x0
> PC (0x7f82c62ad43e) ok
> source "$0x1337" ok
> destination "0x0" (0x00000000) not located in a known VMA region
> (needed writable region)!
> Stack memory exhausted (SP below stack segment)
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: chromium-browser
> StacktraceTop:
> ?? () from /usr/lib/chromium-browser/libs/libcontent.so
> base::MessageLoop::RunTask(base::PendingTask const&) () from
> /usr/lib/chromium-browser/libs/libbase.so
> base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) ()
> from /usr/lib/chromium-browser/libs/libbase.so
> base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from
> /usr/lib/chromium-browser/libs/libbase.so
> ?? () from /usr/lib/chromium-browser/libs/libbase.so
> Title: chromium-browser crashed with SIGSEGV in
> base::Messa...

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.