705003 - ABORT: HangMonitor triggered: file /builds/slave/m-cen-osx64/build/xpcom/threads/HangMonitor.cpp, line 111

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[sci-fi]

Hi,

Several of todays' tinderbox builds for mozilla-central-macosx64 have been crashing.  ("Today" is Wednesday 23-Nov-2011.  Yesterday's builds had no such crash.)

This seems to be related to the Bug 429592 "Hang monitor" patches.

The Nightly Crash Reporter is trying to send the following report, but it keeps saying it is unable to do so (AFAICT; fortunately it is 'copy-&-paste'able):

-* begin *-

AdapterRendererIDs: 
Add-ons: [e-mail]:2.0.13rc,[e-mail]:0.2.9,[e-mail]:1.0,[e-mail]:2.1.2,[e-mail]:2.0.3,[e-mail]:1.19.1,[e-mail]:1.0.1,[e-mail]:2.0development.4,{3d7eb24f-2740-49df-8937-200b1cc08f8a}:1.5.15.1,{73a6fe31-595d-460b-a920-fcc0f8843232}:2.2.1rc3,{b9bfaf1c-a63f-47cd-8b9a-29526ced9060}:1.3.2,{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}:1.3.10,{e0204bd5-9d31-402b-a99d-a6aa8ffebdca}:1.4.4.1,[e-mail]:11.0a1,[e-mail]:1.3.6
BuildID: 20111123101127
CrashTime: 1322089677
EMCheckCompatibility: false
FramePoisonBase: 7ffffffff0dea000
FramePoisonSize: 4096
Hang: 1
InstallTime: 1322086700
Notes: Renderers: GL Context? GL Context+
GL Layers? GL Layers+
xpcom_runtime_abort(###!!! ABORT: HangMonitor triggered: file /builds/slave/m-cen-osx64/build/xpcom/threads/HangMonitor.cpp, line 111)
ProductName: Firefox
ReleaseChannel: default
SecondsSinceLastCrash: 511
StartupTime: 1322089270
Theme: LavaFox_V1-Purple
Throttleable: 1
URL: about:addons
Vendor: Mozilla
Version: 11.0a1

This report also contains technical information about the state of the application when it crashed.

-* end *-

On the console log, we'll see the string inside the xpcom_runtime_abort.  (I didn't see a bug-report based on a few searches of it, so I'll open this one.)

The crash occurs when I leave Nightly alone for a little while (some minutes), whether or not an active window is showing.

That's about all I know.

I'll try disabling the add-ons etc to see if any of them are culprit, too.

Thanks.

Comment 1

[Robert Kaiser]

(In reply to sci-fi from comment #0)
> The Nightly Crash Reporter is trying to send the following report, but it
> keeps saying it is unable to do so (AFAICT; fortunately it is
> 'copy-&-paste'able):

That's unfortunately missing most of the information important to us, like the stack trace.
Could you go to about:crashes, click on the item(s) associated with the time when this happened (if they're not sent, crash reporter will try to send them then) and give us the URL(s) or IDs they link to?

Comment 2

[sci-fi]

Hi,

FWIW I went back to a "good" tinderbox build from Wednesday 23-Nov-2011.

It seems I have about a dozen or so about:crashes reports within this timeframe.  I clicked each one.  It says most 'OOID's cannot be found, but this one seems to be good:

https://crash-stats.mozilla.com/report/index/bp-305eb917-2c82-4245-9f0d-ad1ad2111124

BTW, Starting Nightly with -safe-mode did *not* help anything with this bug, eventually we still got 'pop'd.  ;)

Comment 3

[sci-fi]

(In reply to sci-fi from comment #2)

I see the crashreport I mentioned in comment#2 might be related to Bug 705154, dealing with "@ chromehang | mach_msg_trap", so I put myself on its CC-list and made mention of this bug and the tinderbox builds where it seems to have begun with the Bug 429592 "Hang monitor" patches.

But I am seeing another type of HangMonitor Abort crashreport, this dealing with "@ chromehang | TSFNTFont::GetFormat() const".  Bugzilla doesn't currently show a report with this exact phrase.  Perhaps if this is not directly related to "mach_msg_trap", let's deal with "TSFNTFont::GetFormat" here.  A good report of this is at:

https://crash-stats.mozilla.com/report/index/bp-22e7fd4f-c853-4e70-ab86-3e4202111124

(:bc: sent me a clue how to re-re-re-…-submit the about:crashes reports, so I am presently trying to get them all recorded.  I'll categorise them and put a list of them up if you-all need, soon as I can.)

Comment 4

[sci-fi]

Hi,

Thank you to :bc: for the clue how to re-re-…-submit the about:crashes reports.  Seems mine are all finally recorded.

Here's a list of the 13 reports I have, sectioned according to "Signature" and "Build ID"[1] fields:

Build ID	20111123101127
@ chromehang | TSFNTFont::GetFormat() const 
https://crash-stats.mozilla.com/report/index/bp-22e7fd4f-c853-4e70-ab86-3e4202111124

Build ID	20111123111426
@ chromehang | TSFNTFont::GetFormat() const 
https://crash-stats.mozilla.com/report/index/bp-0055ed42-8ce4-4dbc-a4bf-760e72111124
https://crash-stats.mozilla.com/report/index/bp-9b09a418-0f0a-4893-ac4a-ccc692111124

Build ID	20111123101127
@ chromehang | mach_msg_trap 
https://crash-stats.mozilla.com/report/index/bp-2a77d2f6-39ad-4374-88c7-9c1b72111124
https://crash-stats.mozilla.com/report/index/bp-21f7503b-a058-44c9-a6fc-440042111124
https://crash-stats.mozilla.com/report/index/bp-462950ca-a71b-4f1d-8417-2f2b62111124
https://crash-stats.mozilla.com/report/index/bp-75ba6b07-0c1e-4d08-b124-133472111124
https://crash-stats.mozilla.com/report/index/bp-4a252859-0489-4894-9dc8-df6492111124
https://crash-stats.mozilla.com/report/index/bp-a16632b3-80f9-4fcc-89ed-90fec2111124

Build ID	20111123111426
@ chromehang | mach_msg_trap 
https://crash-stats.mozilla.com/report/index/bp-088853f0-0766-4999-a578-19ada2111124
https://crash-stats.mozilla.com/report/index/bp-521bc212-cbc6-4c54-8e01-6f05a2111124
https://crash-stats.mozilla.com/report/index/bp-15a08077-fc70-41fc-b962-9d8e52111124
https://crash-stats.mozilla.com/report/index/bp-305eb917-2c82-4245-9f0d-ad1ad2111124

[1] - fetched from <https://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-macosx64/?C=M;O=D>

Bug 705154 seems for the "mach_msg_trap".

If "TSFNTFont::GetFormat" is not related, could we perhaps handle it in Bug 705003 to give it a "personality"?

(I'll post this list to both bugs.)

Comment 5

[John Daggett (:jtd)]

I can reproduce this with a testcase I was working on.

Steps:

Load URL in latest nightly.  Data is downloaded and then the tests begin.  This will take a minute or two to complete.  Roughly 30 seconds to a minute after the tests complete, the browser crashes with the error message in the title.

Build identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0a1) Gecko/20111124 Firefox/11.0a1

This may be related to Bug 705258, as that bug also has many crashes with the note above in them.

Comment 6

[John Daggett (:jtd)]

Hmmm, may not even need the testcase, restarting the browser with a new session causes the browser to crash again after a couple minutes of just sitting idle (!?!).

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Comment 8

[Mark Banner (:standard8)]

Bug 705258 is now closed, and Firefox has changed a lot in the last 11 years. I'm closing this out, since I don't think there is anything left here that's useful for us to progress on.