chromium-browser crashed with SIGSEGV in g_main_context_add_poll_unlocked()

Bug #902642 reported by Piotr Sobiesiak
110
This bug affects 15 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

chromium offered instalation of flash plugin. After selection of adobe chromium started instalation of package and then crushed

I installed adobe flash plugin with synaptic package manager

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 15.0.874.120~r108895-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CheckboxSubmission: 126661a92288608699eca7c64bdf5f0a
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
CrashCounter: 1
Date: Sat Dec 10 23:20:37 2011
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 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=plugin\ --plugin-path=/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so\ --lang=pl\ --channel=2084.0xb90bcd10.18269239
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xf21ac9: movw $0x0,0x6(%ebp)
 PC (0x00f21ac9) ok
 source "$0x0" ok
 destination "0x6(%ebp)" (0x00000006) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: chromium-browser crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to precise on 2011-12-10 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Piotr Sobiesiak (sobies) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_main_context_add_poll_unlocked (context=0xb95d42a0, priority=0, fd=0x0) at /build/buildd/glib2.0-2.31.2/./glib/gmain.c:3512
 unblock_source (source=0xb95c35a0) at /build/buildd/glib2.0-2.31.2/./glib/gmain.c:2447
 g_main_dispatch (context=0xb95d42a0) at /build/buildd/glib2.0-2.31.2/./glib/gmain.c:2530
 g_main_context_dispatch (context=0xb95d42a0) at /build/buildd/glib2.0-2.31.2/./glib/gmain.c:3050
 g_main_context_iterate (dispatch=1, block=15934528, context=0xb95d42a0, self=<optimized out>) at /build/buildd/glib2.0-2.31.2/./glib/gmain.c:3121

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
summary: - chromium-browser crashed with SIGSEGV in g_main_context_dispatch()
+ chromium-browser crashed with SIGSEGV in
+ g_main_context_add_poll_unlocked()
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
tags: added: bugpattern-needed
C de-Avillez (hggdh2)
tags: added: qa-manual-testing
C de-Avillez (hggdh2)
visibility: private → public
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.