chromium-browser crashed with SIGSEGV, when renaming a bookmark

[Alexey Rusakov]

Tried to edit a bookmark from my bookmarks panel in Chromium, changed its name (URL stayed intact) and clicked the button. Chromium crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.79~r125985-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 20 11:42:20 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/
Disassembly: => 0x31: Cannot access memory at address 0x31
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: 0x31: Cannot access memory at address 0x31
 PC (0x00000031) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-13 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""

[Alexey Rusakov (ktirf)]

Easily reproduced the crash by trying to edit a bookmark again.

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 HtmlDialogUI::OnDialogClosed(base::ListValue const*) ()
 WebUI::OnWebUISend(GURL const&, std::string const&, base::ListValue const&) ()
 ViewHostMsg_WebUISend::Dispatch<WebUI, WebUI, void (WebUI::*)(GURL const&, std::string const&, base::ListValue const&)> ()
 WebUI::OnMessageReceived(IPC::Message const&) ()

[Alexey Rusakov (ktirf)]

Now that I'm on Raring and running the most recent Chromium, the bug is not reproduced anymore. Not sure how long ago it was fixed - haven't used that functionality for a long time.

[Olivier Tilloy (osomon)]

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.