Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

TBird crashing repeatedly version 45.x and 52.x (OOM)

  • 4 件の返信
  • 1 人がこの問題に困っています
  • 3 回表示
  • 最後の返信者: Wayne Mery

more options

Ever since installing TB v52.1.1 about a week ago, TB has been crashing multiple times a day. It's almost always when I click on a message to display it; usually the message is previously viewed. The message pane (including the headers for the message) will either go completely black, or will redisplay part of the message list from up above; either way, within about 5-10 seconds TB disappears and the crash reporter displays.

I've rebuilt the Global Database and turned off all add-ons (except Lightning), with no apparent impact on the crashing. All the Crash Reasons that I've seen have been one of:

EXCEPTION_ACCESS_VIOLATION_READ EXCEPTION_ACCESS_VIOLATION_WRITE EXCEPTION_BREAKPOINT

I've seen a variety of signatures in the crash reports. An example crash report is f2053e25-1e7a-4a33-a9a7-822c50170522.

I'm available to do testing. I'm a software developer, so I understand the need to test errors and the challenge of tracking down intermittent errors.

Ever since installing TB v52.1.1 about a week ago, TB has been crashing multiple times a day. It's almost always when I click on a message to display it; usually the message is previously viewed. The message pane (including the headers for the message) will either go completely black, or will redisplay part of the message list from up above; either way, within about 5-10 seconds TB disappears and the crash reporter displays. I've rebuilt the Global Database and turned off all add-ons (except Lightning), with no apparent impact on the crashing. All the Crash Reasons that I've seen have been one of: EXCEPTION_ACCESS_VIOLATION_READ EXCEPTION_ACCESS_VIOLATION_WRITE EXCEPTION_BREAKPOINT I've seen a variety of signatures in the crash reports. An example crash report is f2053e25-1e7a-4a33-a9a7-822c50170522. I'm available to do testing. I'm a software developer, so I understand the need to test errors and the challenge of tracking down intermittent errors.

この投稿は Wayne Mery により に変更されました

すべての返信 (4)

more options

Does crashing stop if you start Thunderbird in safe mode? https://support.mozilla.org/en-US/kb/safe-mode-thunderbird

I see you were also crashing frequently when using version 45.x

2017-05-24 18:52:34 	OOM | small   Add term

2017-05-24 15:47:30 CompareCacheMatchEntry Add term 2017-05-23 14:31:57 OOM | small Add term 2017-05-23 01:25:01 CCGraphBuilder::BuildGraph Add term 2017-05-22 21:45:35 OOM | small Add term 2017-05-22 16:51:31 xul.dll@0x11844d4 | xul.dll@0x118c23e | xul.dll@0x1189c1e | xul.dll@0x329a14 | xul.dll@0x33ed8e | xul.dll@0x118510d | xul.dll@0x11701b7 | xul.dll@0x329a14 | xul.dll@0x33ed8e | xul.dll@0x5baf75 | xul.dll@0x5a9d75 | xul.dll@0x5a9b66 | xul.dll@0x32bb06 | ... Add term 2017-05-22 12:34:56 OOM | small Add term 2017-05-15 16:42:13 MimeMultipart_parse_eof Add term 2017-05-11 04:59:24 shutdownhang | ZwFlushBuffersFile Add term 2017-05-01 03:55:40 shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread Add term 2017-04-01 22:02:11 shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread Add term 2017-03-28 07:10:51 shutdownhang | ntdll.dll@0x46c74 Add term 2017-03-23 19:32:16 AtlComPtrAssign Add term 2017-03-23 16:18:34 AtlComPtrAssign Add term 2017-03-15 04:22:59 shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread Add term 2017-03-09 21:48:46 shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread Add term 2017-03-06 02:15:29 shutdownhang | RtlpWaitOnCriticalSection | EtwEventEnabled | arena_dalloc | je_free | nsLocalFile::Release Add term 2017-02-27 02:12:04 shutdownhang | RtlpWaitOnCriticalSection | EtwEventEnabled | arena_malloc_small | arena_malloc | imalloc | je_malloc | js::MallocProvider<T>::pod_malloc<T> Add term 2017-02-23 21:56:48 shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread Add term 2017-02-21 20:43:18 shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread Add term 2017-02-11 04:41:08 shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread Add term 2017-01-27 17:09:29 shutdownhang | js::jit::JitcodeGlobalTable::addEntry Add term 2017-01-12 02:50:46 shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread Add term 2017-01-05 04:25:52 shutdownhang | _PR_MD_WAIT_CV | _PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread Add term 2016-12-29 17:45:47 MimeMultipart_parse_eof Add term 2016-12-28 15:52:33 MimeMultipart_parse_eof Add term

more options

Running in Safe Mode is inconvenient since that disables Lightning, which I use for scheduling. However, I ran Safe Mode overnight. This morning, as I was checking my overnight messages, TB crashed again; report bp-635b42e0-78e9-4399-8bb0-b35160170601. FWIW, this time I didn't see a black message pane before the crash.

I've had crashes before, but nothing approaching the frequency I'm seeing now. I'm usually getting multiple crashes a day; I don't think I've gone a full day without a crash since the update to 52.1.1.

I've noticed that both TB and Firefox seem to be using a lot of memory, as shown in Task Manager. TB is over 400 MB, while I'm seeing Firefox in the 800-900 MB area after several hours, even with a very limited number of windows open.

more options

Update: The program problems continue, both in Safe Mode and regular mode. They're less frequent in Safe Mode, but still happen. This evening, in Safe Mode, it didn't crash, but the display went haywire, with the list of messages redisplayed in the message pane. Attached is an example of what I'm seeing (text blurred for privacy). Interestingly, this time TB didn't crash, and when I displayed a different message, it displayed correctly. However, when I clicked on Reply, I got a new window that was almost completely blacked out. I tried several times and got similar results. I couldn't figure out a way to get a crash-type snapshot of the application, so I simply shut it down and restarted.

I'm also seeing that sometimes a folder, particularly a Trash folder, won't display. When I click on the folder in the folder list, I get the Thunderbird Mail settings page (the page that displays when you click on the account name in the folder list). Sometimes switching to another folder and back will clear the confition.

more options