Particular orbitz page crashes Firefox hard




14 years ago
13 years ago


(Reporter: Clay, Assigned: Blake Ross)



Firefox Tracking Flags

(Not tracked)





14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

A particular page on Orbitz (I'll describe reproducible steps en un momento)
crashes Firefox hard, no passing go, no automagical bug report generator. About
1 out of the 5-7 times I tried this, I was redirected to my home page (which I
then set to blank as a test). The crash seemed to happen, tantalizingly, at the
**end** of rendering this page, at the footer. 

Reproducible: Always

Steps to Reproduce:
< I doubt the actual cities and dates matter here, but I'll give you all my
deets, exactly. Also, b/c of orbitz implementation, any actual URLs deeper in
this process would be useless to you. I'm sure you feel me, yo.>

1. Go to
2. Click "Find low fares for weekends and flexible trips"
3. Select "Option 2: Bonus Days"
4. You are travelling from AUS -> DFW, 13 Feb -> 17 Feb, select "3 days before
and after" on each leg
5. Click "Find"
6. Profit! (i.e. you get the page which renders Firefox into oblivion)

Actual Results:  
cf. details

Expected Results:  
um, not disappear. 

Here is where I thank you, sincerely, for doing this. Hope you can reproduce.
Feel free to contact me if I can help resolve this problem. I'm a coder, and
follow instructions well. I check the email attached to this bug about every 1-2
weeks, so be patient.

Comment 1

14 years ago
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050205

Comment 2

13 years ago
Please provide a talkback id
Keywords: crash

Comment 3

13 years ago
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050420

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.