Closed Bug 204489 Opened 22 years ago Closed 21 years ago

Random crashes in nightlies and 0.6 release

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 234598

People

(Reporter: fv8l1rxj1, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030504 Mozilla Firebird/0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030504 Mozilla Firebird/0.6 Phoenix crashes randomly, I don't know if it's a Phoenix or a Mozilla bug, I'm just looking for someone who can maybe identify the problem using my talkback crash reports. The IDs are TB19799083G and TB19779290Q. The crashes seem random and if someone could have a look into the crashes and where they take place and why, it would be really helpful. Reproducible: Couldn't Reproduce Steps to Reproduce: Crash is Random, not able to reproduce it.
I got another crash, this time using Mozilla Firebird 0.6 Release Version! I was only entering text into a text field and bang, it crashed. However, this time the talkback report is useful, it contains real talkback data! The ID is TB20204051Q If someone could be so kind to fetch the talkback data of this report and post the stack trace here, so we see in which line of code the crash appeared and whether it's a general Mozilla bug or just related to Mozilla Firebird.
Summary: Random crashes in nightlies since middle of April → Random crashes in nightlies and 0.6 release
did the autocomplete dropdown appear when you entering text into that text field? if so, this is a dupe of bug 184202, which is a mozilla bug and already has a stack trace.
No. Sorry that I accidentally said "text field", I actually meant textarea and there is no autocomplete for textareas. Also it didn't happen when I entered the first few characters. I already wrote two pages of text before the crash and auto complete wouldn't kick in that late. Despite that, I don't think it is related to entering text into the textarea, because I experience these random crash more often and they happen in all kind of situations. This time it was entering text into a textarea, but before it happened on a page reload I think (there was a meta refresh tag in the page and after a certain amount of reloads I had the crashes).
Reporter, do you still see "these crashes" ?
Talkback ID: TB23045920Y Talkback ID: TB23045920Y Verified. Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1. Shouldn't matter if you use a textarea or not, been getting this when refreshing a page, and when opening Moz Firebird to report this talkback data.........
QA Contact: asa
I'm also experiencing very frequent crashes with 0.6 and on. I got this one today with 20030910: TB24366365Q. Is this the same bug? I'm not using Mozilla suite anymore so I cannot compare its stability wrt Firebird.
Guys, are you still having crash problems? If so, please download the latest nightly build and see if you find that resolves your problem. Please post your findings in the bug report.
Right now it runs stable on my system, at least there were no crashes the last three weeks and I'm downloading a new nightly weekly. Do you want to close this bug?
I'm seeing quite a few crashes (at various times, not reproducible), but this bug is ancient, so they're probably different crashes. No way of knowing without talkback...
Rare crashes on Win2K, build 20031216. They happen when the visited site has Java code (even then, does not crash consistently). Unfortunately, there's no talkback report. Why is that happening? (I mean the inability of Firebird to initiate a talkback). Is talkbak disabled in recent Firebird builds?
The original bug report doesn't have any steps to reproduce and I cannot replicate this on current builds, duping against bug 234598 for tracking purposes *** This bug has been marked as a duplicate of 234598 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.