Open Bug 1304386 Opened 8 years ago Updated 2 years ago

frequent crashes in [@ arena_dalloc | libc-2.12.so@0x74508 ] when ImapMail directory is on AFS volume that is over quota (short on disk space)

Categories

(MailNews Core :: Database, defect)

x86_64
Linux
defect

Tracking

(Not tracked)

REOPENED

People

(Reporter: goetz.waschk, Unassigned)

Details

(Keywords: crash, Whiteboard: [needs retest])

Crash Data

Attachments

(1 file)

Attached file moz.txt
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160921094759

Steps to reproduce:

changed folder


Actual results:

segmentation fault


Expected results:

no crash
This is on RHEL 6.8. Thunderbird 45.3.0 frequently crashes, 45.2.0 was fine. I am also able to reproduce this in safe mode with all addons disabled.
Severity: normal → critical
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Does it also crash if you use mozilla supplied build from https://archive.mozilla.org/pub/thunderbird/releases/45.3.0/linux-x86_64/ ?
Flags: needinfo?(goetz.waschk)
Keywords: crash
We'd also need a crash ID - https://support.mozilla.org/en-US/kb/mozilla-crash-reporter#w_viewing-crash-reports
Or a file attached with the stacktrace with mozilla symbols
It also crashed with the mozilla build. It has automatically uploaded a crash report, I hope you've received it.
Flags: needinfo?(goetz.waschk)
The crash report in safe mode is this one: https://crash-stats.mozilla.com/report/index/6dfc56f1-fadf-4eb1-9719-f47d22160922
Crash Signature: [@ arena_dalloc | libc-2.12.so@0x74508 ]
Summary: frequent crashes → frequent crashes in [@ arena_dalloc | libc-2.12.so@0x74508 ]
Thanks.

bp-6dfc56f1-fadf-4eb1-9719-f47d22160922
 0 	thunderbird	arena_dalloc	memory/mozjemalloc/jemalloc.c:4725
Ø 1 	libc-2.12.so	libc-2.12.so@0x74508	
Ø 2 	libc-2.12.so	libc-2.12.so@0x726f2	
Ø 3 	libc-2.12.so	libc-2.12.so@0x664b7	
4 	libxul.so	morkStdioFile::CloseStdio(morkEnv*)	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkFile.cpp:844
5 	libxul.so	morkStdioFile::CloseStdioFile(morkEnv*)	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkFile.cpp:381
6 	libxul.so	morkStdioFile::~morkStdioFile()	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkFile.cpp:368
7 	libxul.so	morkStdioFile::~morkStdioFile()	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkFile.cpp:370
8 	libxul.so	morkObject::Release()	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkObject.cpp:35
9 	libxul.so	morkStore::CloseStore(morkEnv*)	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkStore.cpp:234
10 	libxul.so	morkStore::CloseMorkNode(morkEnv*)	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkStore.cpp:109
11 	libxul.so	morkStore::~morkStore()	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkStore.cpp:138
12 	libxul.so	morkStore::~morkStore()	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkStore.cpp:150
13 	libxul.so	morkObject::Release()	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/db/mork/src/morkObject.cpp:35
14 	libxul.so	nsMsgDatabase::~nsMsgDatabase()	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/mailnews/db/msgdb/src/nsMsgDatabase.cpp:1164
15 	libxul.so	nsImapMailDatabase::~nsImapMailDatabase()	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/mailnews/db/msgdb/src/nsImapMailDatabase.cpp:23
16 	libxul.so	nsMsgDatabase::Release()	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/mailnews/db/msgdb/src/nsMsgDatabase.cpp:1174
17 	libxul.so	nsAutoSyncState::ProcessExistingHeaders(unsigned int, unsigned int*)	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/mailnews/imap/src/nsAutoSyncState.cpp:388
18 	libxul.so	nsAutoSyncManager::TimerCallback(nsITimer*, void*)	/builds/slave/tb-rel-c-esr45-l64_bld-0000000/build/mailnews/imap/src/nsAutoSyncManager.cpp:297
Status: UNCONFIRMED → NEW
Component: Untriaged → Database
Ever confirmed: true
Product: Thunderbird → MailNews Core
Version: 45 Branch → 45
I think I have found the cause: the ImapMail directory is on an AFS volume that was over quota. I have deleted the contents and there wasn't a crash yet.
(In reply to goetz.waschk from comment #7)
> I think I have found the cause: the ImapMail directory is on an AFS volume
> that was over quota. I have deleted the contents and there wasn't a crash
> yet.

Thanks!
Summary: frequent crashes in [@ arena_dalloc | libc-2.12.so@0x74508 ] → frequent crashes in [@ arena_dalloc | libc-2.12.so@0x74508 ] when ImapMail directory is on AFS volume that is over quota
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #8)
> (In reply to goetz.waschk from comment #7)
> > I think I have found the cause: the ImapMail directory is on an AFS volume
> > that was over quota. I have deleted the contents and there wasn't a crash
> > yet.
> 
> Thanks!

I think the code should not crash in the face of AFS volume that is over quota.
Somewhere proper error checking is not performed.
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: frequent crashes in [@ arena_dalloc | libc-2.12.so@0x74508 ] when ImapMail directory is on AFS volume that is over quota → frequent crashes in [@ arena_dalloc | libc-2.12.so@0x74508 ] when ImapMail directory is on AFS volume that is over quota (short on disk space)
Severity: critical → normal
Whiteboard: [needs retest]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: