Closed Bug 492671 Opened 15 years ago Closed 15 years ago

browser freezing during runtime/shutdown on leopard/tiger/vista with new pageset

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 483902

People

(Reporter: anodelman, Assigned: anodelman)

References

Details

Browser hangs during shutdown running Tp3 with the new pageset.  Happens every run with tiger/leopard, intermittently on vista.

Will attempt to collect a stack trace to isolate the cause.
Blocks: 473821
Summary: browser freezing during shutdown on mac/tiger/vista with new pageset → browser freezing during shutdown on leopard/tiger/vista with new pageset
From irc, Alice confirmed this does not hang on linux.
Freezing during more than shutdown, unfortunately.

I'm pursing installing debugging tools on vista to see if I can get a stacktrace there.  Getting crashstacks on macs for frozen browsers has already been investigated by ted with no success, so I'm going to ignore the freezing there for now.
Summary: browser freezing during shutdown on leopard/tiger/vista with new pageset → browser freezing during runtime/shutdown on leopard/tiger/vista with new pageset
Can we point dtrace at the frozen process, or install something like pstack?  that'll require some munging since it won't have symbols, but it should give us the raw data back.
try <code>sudo dtrace -n 'pid1069:::entry { ustack() }'</code> replacing pid1069 with whatever pid you really have.  this will generate a TON of output though.
I'm still attempting to get a stack trace from vista (which is about as fun as it sounds), and also collecting a dtrace long on leopard.  I'll post whichever becomes available first.
How much of the dtrace log is worthwhile?  It's really, really huge and if only the last 1000 lines are interesting I'd rather not have to deal with moving around the whole thing.
Here's a chunk of the log to show the sort of thing that it is collecting:

http://pastebin.mozilla.org/650372
That's plenty to implicate Joe Drew, I think!
That's spurious imagelib stuff. Henri saw similar crashes in his HTML5 parser build, but it's all because of bad backtracing.
Still attempting to get a stack snapshot once the browser is frozen on vista.  Involves installing debugging tools on the platform and integrating into talos - if I'm lucky I could get evidence as to where it's getting stuck.
Much better than a stack snapshot would be a full-options minidump from ntsd -- with that we have a much better chance of fixing the bug without reproducing on a developer workstation.
Assigning to myself for now, but this should really get on a developers list.  We'd be happy to provide support in reproducing the bug, but could use help in finding the root cause and then getting that fixed.
Assignee: nobody → anodelman
Priority: -- → P2
ntsd comes with a VBScript thing that you can run after the process is hung (perhaps at the point at which you'd normally kill it?) and will produce the desired minidump.  At that point, we will point the full force of engineering at it. :)
(In reply to comment #12)
> Assigning to myself for now, but this should really get on a developers list. 
> We'd be happy to provide support in reproducing the bug, but could use help in
> finding the root cause and then getting that fixed.

Michal: Is this a DUP of bug#483902?
It seems so. What I've written in https://bugzilla.mozilla.org/show_bug.cgi?id=483902#c17 doesn't explain why the browser is freezing (and mine has always ended with result "FAIL" instead of freezing...) but IMHO this is a undefined state when browser can't open any additional file, socket etc. so everything is possible...
I'm using cdb (pretty much ntsd by another name) to attempt to generate a minidump from a frozen browser.  I think that i'm thisclose to getting it working, but I'd be just as happy to have this fixed by the other bug.
I'll move my work using cdb to collect crash stacks from frozen browsers to another bug.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.