abrt 1.0.7 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/thunderbird-3.0/thunderbird-bin comment: I'm not sure what triggered this; I was in the middle of reading mail from an IMAP server that had just been filtered into a local folder, while new mail was still being processed. component: thunderbird executable: /usr/lib/thunderbird-3.0/thunderbird-bin kernel: 2.6.32.9-67.fc12.i686 package: thunderbird-3.0.3-1.fc12 rating: 4 reason: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 398818 [details] File: backtrace
#3 <signal handler called> No symbol table info available. #4 nsMsgSearchOfflineMail::ProcessSearchTerm (msgToMatch=0x0, aTerm= 0xb4abd040, defaultCharset=0xb3cfeda8 "ISO-8859-1", scope=0xa40d31f0, db= 0xa42717c0, headers=0x0, headerSize=0, Filtering=1, pResult=0xbf8b3550) at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mailnews/base/search/src/nsMsgLocalSearch.cpp:457 err = 0 ccList = {<nsACString_internal> = {mData = 0x5a628ec "", mLength = 0, mFlags = 1}, <No data fields>} msgCharset = {<nsACString_internal> = {mData = 0x5a628ec "", mLength = 0, mFlags = 1}, <No data fields>} matchAll = 0 recipients = {<nsACString_internal> = {mData = 0x5a628ec "", mLength = 0, mFlags = 1}, <No data fields>} charset = <value optimized out> charsetOverride = 0 attrib = <value optimized out> matchString = {<nsACString_internal> = {mData = 0x5a628ec "", mLength = 0, mFlags = 1}, <No data fields>} msgFlags = <value optimized out> result = <value optimized out> #5 0x015e510a in nsMsgSearchBoolExpression::OfflineEvaluate ( this=0xb044e600, msgToMatch=0x0, defaultCharset=0xb3cfeda8 "ISO-8859-1", scope=0xa40d31f0, db=0xa42717c0, headers=0x0, headerSize=0, Filtering=1) at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mailnews/base/search/src/nsMsgLocalSearch.cpp:171 result = 0 #6 0x015e5504 in nsMsgSearchOfflineMail::MatchTerms (msgToMatch=0x0, termList=0xb4aafa40, defaultCharset=0xb3cfeda8 "ISO-8859-1", scope=0xa40d31f0, db=0xa42717c0, headers=0x0, headerSize=0, Filtering=1, aExpressionTree=0xb4a981f0, pResult=0xbf8b36a0) at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mailnews/base/search/src/nsMsgLocalSearch.cpp:719 err = <value optimized out> #7 0x015e58e9 in nsMsgSearchOfflineMail::MatchTermsForFilter ( msgToMatch=0x0, termList=0xb4aafa40, defaultCharset=0xb3cfeda8 "ISO-8859-1", scope=0xa40d31f0, db=0xa42717c0, headers=0x0, headerSize=0, aExpressionTree=0xb4a981f0, pResult=0xbf8b36a0) at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mailnews/base/search/src/nsMsgLocalSearch.cpp:348 No locals. #8 0x015ddda6 in nsMsgFilter::MatchHdr (this=0xb4a98160, msgHdr=0x0, folder=0xb3ceb020, db=0xa42717c0, headers=0x0, headersSize=0, pResult=0xbf8b36a0) at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mailnews/base/search/src/nsMsgFilter.cpp:641 folderCharset = {<nsACString_internal> = { mData = 0xb3cfeda8 "ISO-8859-1", mLength = 10, mFlags = 5}, <No data fields>} rv = 3031007584 #9 0x015db0f1 in nsMsgFilterList::ApplyFiltersToHdr (this=0xb4a5fbf0, filterType=1, msgHdr=0x0, folder=0xb3ceb020, db=0xa42717c0, headers=0x0, headersSize=0, listener=0xb3ceb13c, msgWindow=0x0, aMessageFile=0x0) at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mailnews/base/search/src/nsMsgFilterList.cpp:354 matchTermStatus = 0 result = 22492309 isEnabled = 1 curFilterType = 17 filterIndex = 0 filter = {<nsCOMPtr_base> = {mRawPtr = 0xb4a98160}, <No data fields>} filterCount = 32 rv = 0 scope = 0xa40d31f0 -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Reporter, was this a one-time event, or can you reliably reproduce it? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I don't know whether I can reliably reproduce it, but it does seem like it has happened to me more than once. Anything in particular I should pay attention to next time it happens?
We are only after the steps how to reproduce this bug on our computers. If there is anything which could help us in doing that would be important? Something special about your configuration, system, networking, etc.? Thank you in advance for any response
In my case, the IMAP server that I am accessing is behind a VPN. I've noticed the crash is most likely to happen when I first connect to the VPN, such that thunderbird has a large backlog of messages to process from the server. I also have a number of mail filters which move messages out of the IMAP folder into local folders, and are trying to expunge the original on the server as soon as the move happens. Perhaps it is a threading interaction between one thread attempting to do the filtering while another thread is still trying to contact the IMAP server.
*** Bug 590717 has been marked as a duplicate of this bug. ***
*** Bug 593705 has been marked as a duplicate of this bug. ***
*** Bug 609504 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.