chromium-browser crashed with SIGSEGV in __get_nprocs()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
just after closing chrome browser
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: chromium-browser 28.0.1500.
ProcVersionSign
Uname: Linux 3.11.0-2-generic i686
NonfreeKernelMo
ApportVersion: 2.12-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Tue Aug 27 22:43:15 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/
MarkForUpload: True
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
SegvAnalysis:
Segfault happened at: 0xb05914bd <__get_nprocs+109>: movl $0x80000,0x4(%esp)
PC (0xb05914bd) ok
source "$0x80000" ok
destination "0x4(%esp)" (0xabdfe574) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
__get_nprocs () at ../sysdeps/
arena_get2 (avoid_arena=0x0, size=<optimised out>, a_tsd=<optimised out>) at arena.c:848
arena_get2 (a_tsd=<optimised out>, size=<optimised out>, avoid_arena=0x0) at arena.c:831
__GI___libc_malloc (bytes=43) at malloc.c:2856
malloc () from /usr/lib/
Title: chromium-browser crashed with SIGSEGV in __get_nprocs()
UpgradeStatus: Upgraded to saucy on 2013-06-15 (73 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy libvirtd lpadmin netdev plugdev powerdev sambashare scanner video
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1195797, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.