Description of problem: SM crashed in usual work, in this case I just want edit some filter rule. Crash occur when I click on Edit (rule) button. Then HDD for a moment began to work, and then crash occurs. IMO SM (as well as other Mozilla products) has enormous memory demands, and are not able work with larger mail accounts and/or lots of browser windows and tabs. I have two mail accounts with ~ 2 million mails, and want work with several tens of browser windows and several tens tabs in each window. Logs created in HTML IMO are memory hungry too. Version-Release number of selected component: seamonkey-2.24-1.fc19 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/lib/seamonkey/seamonkey crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib/seamonkey/seamonkey kernel: 3.13.6-100.fc19.i686.PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 nsProfileLock::FatalSignalHandler at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/profile/dirserviceprovider/src/nsProfileLock.cpp:180 #3 AsmJSFaultHandler at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/js/src/jit/AsmJSSignalHandlers.cpp:988 #5 mozalloc_abort at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/memory/mozalloc/mozalloc_abort.cpp:30 #6 mozalloc_handle_oom at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/memory/mozalloc/mozalloc_oom.cpp:50 #7 moz_xmalloc at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/memory/mozalloc/mozalloc.cpp:56 #8 NS_Alloc at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/xpcom/base/nsMemoryImpl.cpp:196 #9 nsMemoryImpl::Alloc at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/xpcom/base/nsMemoryImpl.cpp:33 #10 nsSegmentedBuffer::AppendNewSegment at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/xpcom/io/nsSegmentedBuffer.cpp:71 #11 nsPipe::GetWriteSegment at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/xpcom/io/nsPipe3.cpp:465 #12 nsPipeOutputStream::WriteSegments at /usr/src/debug/seamonkey-2.24/comm-release/mozilla/xpcom/io/nsPipe3.cpp:1086
Created attachment 880525 [details] File: backtrace
Created attachment 880526 [details] File: cgroup
Created attachment 880527 [details] File: core_backtrace
Created attachment 880528 [details] File: dso_list
Created attachment 880529 [details] File: environ
Created attachment 880530 [details] File: limits
Created attachment 880531 [details] File: maps
Created attachment 880532 [details] File: open_fds
Created attachment 880533 [details] File: proc_pid_status
Created attachment 880534 [details] File: var_log_messages
Another user experienced a similar problem: crash occurs (repeatedly) when I select filtering rule and then click on "Edit" button (I want edit some rule). reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/lib/seamonkey/seamonkey crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib/seamonkey/seamonkey kernel: 3.13.9-100.fc19.i686.PAE package: seamonkey-2.25-1.fc19 reason: seamonkey killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This is an automated bug update. We don't use Abrt for tracking Firefox bugs so it may be a crash in other component like plugin-container. If you can reproduce the issue, please remove the [abrt] string from summary and reopen it. Thanks!