abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: midori component: midori crash_function: WTF::OSAllocator::reserveAndCommit executable: /usr/bin/midori kernel: 2.6.35.10-74.fc14.x86_64 package: midori-0.2.9-4.fc14 rating: 4 reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1296347666 uid: 500 comment ----- Midori was never installed on this machine, so no forgotten config files could do this. Also, when I attempt to start it again, some dialog window appears, telling me that Midori did not exit properly last time. When starting from terminal, it prints (sorry for possible mistranslation): Unauthorized memory access (SIGSEGV) (core dumped) How to reproduce ----- 1. Install Midori from oficial repos 2. Attempt to start it, either from terminal, xfrun4 or applications menu 3. Wait a while, crash appears
Created attachment 475993 [details] File: backtrace
If you do: echo 1 > /proc/sys/vm/overcommit_memory does it start working again normally?
Yes, browser starts normally now. But I can't test how it behaves after reboot..
This looks like another case of 648319 (a webkitgtk bug). The above works around it, and there's going to be a fix in the next upstream release. *** This bug has been marked as a duplicate of bug 648319 ***