chromium-browser crashed with SIGSEGV in RenderWidgetHostViewGtkWidget::OnButtonPressReleaseEvent()

Bug #919483 reported by cariboo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Every time I go to a web site using https and it doesn't have a valid security certificate chromium-browser crashes. This includes my Linksys 310n router.

The last time it happened I went to:

midnight-commander.org

The warning screen about an invalid security certificate came up, then chromium-browser greyed out, and eventually crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 15.0.874.120~r108895-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CheckboxSubmission: 6fd39f33eec9cabdbad42b1d6d866fdb
CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
Date: Fri Jan 20 17:21:25 2012
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 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fa19584ac4d: mov (%rax),%rax
 PC (0x7fa19584ac4d) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: chromium-browser crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2012-01-10 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
cariboo (cariboo) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 RenderWidgetHostViewGtkWidget::OnButtonPressReleaseEvent(_GtkWidget*, _GdkEventButton*, RenderWidgetHostViewGtk*) ()
 _gtk_marshal_BOOLEAN__BOXED (closure=0x7fa19d145db0, return_value=0x7fff90704330, n_param_values=<optimized out>, param_values=0x7fa19b7fd580, invocation_hint=<optimized out>, marshal_data=<optimized out>) at /build/buildd/gtk+2.0-2.24.8/gtk/gtkmarshalers.c:86
 g_closure_invoke (closure=0x7fa19d145db0, return_value=0x7fff90704330, n_param_values=2, param_values=0x7fa19b7fd580, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.10/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=<optimized out>, emission_return=0x7fff90704470, instance_and_params=0x7fa19b7fd580) at /build/buildd/glib2.0-2.31.10/./gobject/gsignal.c:3302
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=0x7fff907044d8) at /build/buildd/glib2.0-2.31.10/./gobject/gsignal.c:3043

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_closure_invoke()
+ chromium-browser crashed with SIGSEGV in
+ RenderWidgetHostViewGtkWidget::OnButtonPressReleaseEvent()
tags: removed: need-amd64-retrace
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: New → 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.