I can by launching gwibber-accounts,click add, select twitter, click add, click authorize.
This will try to use webkit to open the twitter page, which then segfaults.
echo 1 > /proc/sys/vm/overcommit_memory fixes this until reboot.
here is a backtrace: http://launchpadlibrarian.net/63485933/gdb-gwibber-accounts.txt here is a valgrind log: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/704393/+attachment/1827136/+files/gwibber-accounts-valgrind.log
This crash is happening because webkit is allocating 2GB's of memory with mmap and presumes the os to do overcomminting of memory. If you have enought free memory (or swap) then webkit might not crash at all.
I can by launching gwibber- accounts, click add, select twitter, click add, click authorize.
This will try to use webkit to open the twitter page, which then segfaults.
echo 1 > /proc/sys/ vm/overcommit_ memory
fixes this until reboot.
here is a backtrace: launchpadlibrar ian.net/ 63485933/ gdb-gwibber- accounts. txt /bugs.launchpad .net/ubuntu/ +source/ epiphany- browser/ +bug/704393/ +attachment/ 1827136/ +files/ gwibber- accounts- valgrind. log
http://
here is a valgrind log:
https:/
This crash is happening because webkit is allocating 2GB's of memory with mmap and presumes the os to do overcomminting of memory. If you have enought free memory (or swap) then webkit might not crash at all.