crash with "reload every" extension and two tabs, one with password autocomplete




14 years ago
14 years ago


(Reporter: Robert Freund, Assigned: Blake Ross)


Firefox Tracking Flags

(Not tracked)




14 years ago
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040212 Firefox/0.8

I experienced a crash after logging in on some web form on one page, enabling
"reload every" on that page, and then opening another web form for which firefox
knows my username/password in another tab, and then closing this second tab.

If you look at the "steps to reproduce", I must admit that this is a pretty
special situation. I just think that since the "reload every" extension is
obviously involved in this crash, why should firefox be crashable by extensions?

Reproducible: Always
Steps to Reproduce:
1. install extension "reload every"
2. start firefox without any pages (!no homepage!)
3. go to a page where you need to login (like an email service), then perform
the login, and then enable "reload every" via the right mouse button menu
4. open a new tab, and go to a page where you have your username/password stored
in firefox (but don't login)
5. after the second page has fully loaded, close it by clicking the close button
to the right of the tabs

(note that you need to do it exactly in this order. any browsing inbetween will
prevent firefox from crashing)
Actual Results:  
Firefox crashed:
firefox exited with non-zero status (11)

Comment 1

14 years ago
Often extensions are the problem, but that is not a FF bug, but a bug in the
extension - to be reported to them, not here.  If it only happens with the
extension, this bug is invalid.  Can you test and report back?

Comment 2

14 years ago
Reporter, we cannot proceed with this bug without your response to the above
query. Please comment on this bug with additional information, by visiting the
URL referenced in this email, within 5 days. If this doesn't happen, this bug
will be marked INVALID. Thanks :-)

Comment 3

14 years ago
Marked INVALID as reporter did not respond after a long period of time. 
Reporter, should you feel the need to do so, REOPEN this bug.
Last Resolved: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.