Description of problem: I was just scrolling down a page when the program crashed. Version-Release number of selected component: firefox-26.0-2.fc19 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/lib/firefox/firefox crash_function: __kernel_vsyscall executable: /usr/lib/firefox/firefox kernel: 3.12.5-200.fc19.i686.PAE runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Dec 31 17:42:01 khorlia abrt-hook-ccpp[12469]: Saved core dump of pid 6147 (/usr/lib/firefox/firefox) to /var/tmp/abrt/ccpp-2013-12-31-17:41:43-6147 (773095424 bytes) Truncated backtrace: Thread no. 3 (10 frames) #0 __kernel_vsyscall #1 poll at ../sysdeps/unix/syscall-template.S:81 #3 _pr_poll_with_poll at ../../../nspr/pr/src/pthreads/ptio.c:3920 #4 nsSocketTransportService::Poll at /usr/src/debug/xulrunner-26.0/mozilla-release/netwerk/base/src/nsSocketTransportService2.cpp:394 #5 nsSocketTransportService::DoPollIteration at /usr/src/debug/xulrunner-26.0/mozilla-release/netwerk/base/src/nsSocketTransportService2.cpp:806 #6 nsSocketTransportService::Run at /usr/src/debug/xulrunner-26.0/mozilla-release/netwerk/base/src/nsSocketTransportService2.cpp:670 #7 nsThread::ProcessNextEvent at /usr/src/debug/xulrunner-26.0/mozilla-release/xpcom/threads/nsThread.cpp:622 #8 NS_ProcessNextEvent at /usr/src/debug/xulrunner-26.0/mozilla-release/xpcom/glue/nsThreadUtils.cpp:238 #9 nsThread::ThreadFunc at /usr/src/debug/xulrunner-26.0/mozilla-release/xpcom/threads/nsThread.cpp:250 #10 _pt_root at ../../../nspr/pr/src/pthreads/ptthread.c:204
Created attachment 844055 [details] File: backtrace
Created attachment 844056 [details] File: cgroup
Created attachment 844057 [details] File: core_backtrace
Created attachment 844058 [details] File: dso_list
Created attachment 844059 [details] File: environ
Created attachment 844060 [details] File: limits
Created attachment 844061 [details] File: maps
Created attachment 844062 [details] File: open_fds
Created attachment 844063 [details] File: proc_pid_status
This is an automated bug update. If you can reproduce the bug, please reopen and remove the [abrt] string from subject. Thanks!
It only happened the one time, and I've no idea why or how.