Closed Bug 266747 Opened 20 years ago Closed 20 years ago

crash when visiting rexplex.com

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mozbug1, Unassigned)

References

()

Details

(Keywords: crash)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913

Mozilla 1.7.3 crashes when visiting rexplex.com.  Firefox 1rc1 does not.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Does a current trunk nightly crash?  For that matter, does a current branch nightly?
Summary: crash when visiting rexplex.com → crash when visiting rexplex.com
WFM 20041101/trunk/W2K
Product: Browser → Seamonkey
Works with 1.8a5 while 1.7.3 is still crashing, so I'm marking as fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
It's "worksforme" if we don't know what fixed it...
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → WORKSFORME
This bug appears in the current firefox, but not mozilla 1.7.5. Reopening.
Status: RESOLVED → UNCONFIRMED
Product: Mozilla Application Suite → Firefox
Resolution: WORKSFORME → ---
Version: Trunk → 1.0 Branch
Reporter: please provide a stack trace, or lacking that, a talkback ID.

/be
How do I get the talkbalk id?
Get a talkback-enabled build, install it agreeing to turn on the quality
feedback agent, crash the program, agree to send the talkback report, etc.

/be
(In reply to comment #5)
> This bug appears in the current firefox, but not mozilla 1.7.5. Reopening.

I assume "current" here means "trunk", not "1.0"?
No, I meant 1.0.

Talkbalk is not showing me an id number.  I just disappears after I hit send or
details, I have no way of knowing if it actualy sent anything.
I just tried rexplex.com with firefox 1.0 on a suse 9.1 machine and it had no
problems.  This is a redhat 9 machine.
you can run the talkback binary in <install dir>/components/talkback to see the
number
OK talkbalk id tb2791993q
Please do retest with a current trunk Firefox build.  The crash looks like the
standard "null cell-inner frame" issue, which has been fixed on trunk.
Works fine on the nightly build I downloaded.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: