Severity: normal → critical
OS: Windows 2000 → All
Hardware: PC → All
Setting default owner and QA -
Assignee: rogerl → pchen
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: pschwartau → sairuh
I'm the reporter and I have a question that is unrelated to that bug in particular, but related to bugs like this one. I end up often with Mozilla taking 99% CPU. Usually I do not report them because I do not find their origin and can't reproduce them. Are there any methods for retrieving some information about the actual state of the program so that I can report a bug with some information? The problem is that I am on W2k and don't know a lot the commands... Perhaps using some of Visual C++ Tools? Should I use Talkback and generate a report? Are there any help on the Mozilla Web site saying how to help you investigate those bugs?
actually, talkback only generates a report when the app crashes, not when it hangs. :(
Severity: critical → major
Priority: -- → P2
Target Milestone: --- → mozilla0.9.7
Marking p2, major, and mozilla0.9.7.
*** This bug has been marked as a duplicate of 85831 ***
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE
mass verification of duplicate bugs: to find all bugspam pertaining to this, set your search string to "DuplicateBugsBelongInZahadum". if you think this particular bug is *not* a duplicate, please provide a compelling reason, as well as check a recent *trunk* build (on the appropriate platform[s]), before reopening.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.