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 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::MessageLoop::RunTask()
>> UpgradeStatus: No upgrade log present (probably fresh install)
>> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>> chromium-default:
>> CHROMIUM_FLAGS=""
>> . /usr/lib/pepflashplugin-installer/pepflashplayer.sh
>> mtime.conffile..etc.chromium.browser.default: 2013-11-10T15:09:15.272458
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/chromium-browser/+bug/1250174/+subscriptions
>>
>
>
This is probably the thread the controlling process thinks is hung.
Thread 3 (Thread 0x7f82b7d36980 (LWP 4925)): 64-linux- gnu/libc. so.6 x86_64- linux-gnu/ libdrm. so.2 gem_bo_ start_gtt_ access () from x86_64- linux-gnu/ libdrm_ intel.so. 1 x86_64- linux-gnu/ dri/i965_ dri.so x86_64- linux-gnu/ dri/i965_ dri.so x86_64- linux-gnu/ dri/i965_ dri.so x86_64- linux-gnu/ mesa/libGL. so.1 eadSGI () from x86_64- linux-gnu/ mesa/libGL. so.1 chromium- browser/ libs/libgl_ wrapper. so chromium- browser/ libs/libgpu. so chromium- browser/ libs/libcontent .so
#0 0x00007f82badb6c67 in ioctl () from /lib/x86_
No symbol table info available.
#1 0x00007f82b55c62b8 in drmIoctl () from
/usr/lib/
No symbol table info available.
#2 0x00007f82b4b1049f in drm_intel_
/usr/lib/
No symbol table info available.
#3 0x00007f82b531164a in ?? () from
/usr/lib/
No symbol table info available.
#4 0x00007f82b5312671 in ?? () from
/usr/lib/
No symbol table info available.
#5 0x00007f82b5399baf in ?? () from
/usr/lib/
No symbol table info available.
#6 0x00007f82b6259d7f in ?? () from
/usr/lib/
No symbol table info available.
#7 0x00007f82b6231563 in glXMakeCurrentR
/usr/lib/
No symbol table info available.
#8 0x00007f82c4a13894 in ?? () from
/usr/lib/
No symbol table info available.
#9 0x00007f82c6b5d4e7 in ?? () from
/usr/lib/
No symbol table info available.
#10 0x00007f82c6271503 in ?? () from
/usr/lib/
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 /bugs.launchpad .net/bugs/ 1250174 :GpuWatchdogThr ead::Deliberate lyTerminateToRe coverFromHang( ) 114-0ubuntu0. 12.04.3 ature: Ubuntu 3.8.0-33. 48~precise1- generic 3.8.13.11 .config/ chromium/ Default/ Preferences xdg-ubuntu: /etc/xdg ubuntu: /usr/share/ gnome:/ usr/local/ share/: /usr/share/ chromium- browser/ chromium- browser chromium- browser/ chromium- browser\ 4656.10. 459810737\ dual-gpus= false\ --gpu-driver- bug-workarounds =0,6,18\ id=0x8086\ --gpu-device- id=0x0106\ --gpu-driver- vendor= Mesa\ version= 9.1.7 chromium- browser/ libs/libcontent .so op::RunTask( base::PendingTa sk const&) () from chromium- browser/ libs/libbase. so op::DeferOrRunP endingTask( base::PendingTa sk const&) () chromium- browser/ libs/libbase. so op::DoDelayedWo rk(base: :TimeTicks* ) () from chromium- browser/ libs/libbase. so chromium- browser/ libs/libbase. so op::RunTask( ) pepflashplugin- installer/ pepflashplayer. sh .etc.chromium. browser. default: 2013-11- 10T15:09: 15.272458 /bugs.launchpad .net/chromium- browser/ +bug/1250174/ +subscriptions
> 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:/
>>
>> Title:
>> chromium-browser crashed with SIGSEGV in
>> content:
>>
>> 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.
>> ProcVersionSign
>> Uname: Linux 3.8.0-33-generic x86_64
>> ApportVersion: 2.0.1-0ubuntu17.6
>> Architecture: amd64
>> ChromiumPrefs: can't open profile
>> /home/jamesmaz/
>> Date: Mon Nov 11 13:10:09 2013
>> Desktop-Session:
>> DESKTOP_SESSION = ubuntu
>> XDG_CONFIG_DIRS = /etc/xdg/
>> XDG_DATA_DIRS =
>> /usr/share/
>> Env:
>> MOZ_PLUGIN_PATH = None
>> LD_LIBRARY_PATH = None
>> ExecutablePath: /usr/lib/
>> InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release
>> amd64 (20130820.1)
>> MarkForUpload: True
>> ProcCmdline: /usr/lib/
>> --type=gpu-process\ --channel=
>> --supports-
>> --gpu-vendor-
>> --gpu-driver-
>> 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/
>> base::MessageLo
>> /usr/lib/
>> base::MessageLo
>> from /usr/lib/
>> base::MessageLo
>> /usr/lib/
>> ?? () from /usr/lib/
>> Title: chromium-browser crashed with SIGSEGV in
>> base::MessageLo
>> UpgradeStatus: No upgrade log present (probably fresh install)
>> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>> chromium-default:
>> CHROMIUM_FLAGS=""
>> . /usr/lib/
>> mtime.conffile.
>>
>> To manage notifications about this bug go to:
>> https:/
>>
>
>