Bug 53684 - libwebkitgtk-1.0-0 crashes on amd64 architecture with SIGSEGV in WTF::OSAllocator::reserveAndCommit()
Summary: libwebkitgtk-1.0-0 crashes on amd64 architecture with SIGSEGV in WTF::OSAlloc...
Status: RESOLVED DUPLICATE of bug 42756
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 420+
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL: https://bugs.launchpad.net/ubuntu/+so...
Keywords: Gtk
Depends on:
Blocks:
 
Reported: 2011-02-03 08:10 PST by jens.timmerman
Modified: 2011-02-03 12:27 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jens.timmerman 2011-02-03 08:10:52 PST 
Users of ubuntu natty are experiencing a sigsegv of libwebkitgtk-1.0-0 in  WTF::OSAllocator::reserveAndCommit()  on amd64 platforms.
The original bug report was made here:
https://bugs.launchpad.net/ubuntu/+source/webkit/+bug/710582 

a backtrace kan be found here:
http://launchpadlibrarian.net/63485933/gdb-gwibber-accounts.txt
and a valgrind log here:
https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/704393/+attachment/1827136/+files/gwibber-accounts-valgrind.log

several people can reproduce this bug. F.ex by starting up gwibber-accounts and trying to add a new twitter account. Or by using the ubiquity installer.
Comment 1 Martin Robinson 2011-02-03 11:33:43 PST 
I think this might be a dupe. CCing Xan who should definitely know.
Comment 2 Xan Lopez 2011-02-03 12:09:14 PST 
The trace is different, but it definitely looks like bug 42756. To double check enable overcommit and see if it stops happening (echo 1 > /proc/sys/vm/overcommit).
Comment 3 jens.timmerman 2011-02-03 12:23:57 PST 
echo 1 > /proc/sys/vm/overcommit_memory
does fix the problem!
Comment 4 Martin Robinson 2011-02-03 12:27:21 PST 
Thanks for reporting this issue! Please refer to the earlier issue for updates.

*** This bug has been marked as a duplicate of bug 42756 ***