chromium-browser crashed with SIGSEGV in __get_nprocs()

Bug #1217574 reported by Hans Ginzel
16
This bug affects 2 people
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.71-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic i686
NonfreeKernelModules: nvidia
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-ubuntu:/usr/share/upstart/xdg:/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
MarkForUpload: True
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=11953.9.1498203940\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=0,20,22\ --gpu-vendor-id=0x10de\ --gpu-device-id=0x0421\ --gpu-driver-vendor=NVIDIA\ --gpu-driver-version=304.
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/unix/sysv/linux/getsysstats.c:151
 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/chromium-browser/libs/libbase.so
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/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox %u\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %u\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b'compiz\n'/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

Revision history for this message
Hans Ginzel (hans-matfyz) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Olivier Tilloy (osomon) wrote :

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.

Changed in chromium-browser (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.