linux-traipu team mailing list archive
-
linux-traipu team
-
Mailing list archive
-
Message #10006
[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 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 member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
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
Follow ups