Closed Bug 264747 Opened 20 years ago Closed 20 years ago

Firefox crashes when using Typeaheadfind

Categories

(Toolkit :: Find Toolbar, defect)

1.7 Branch
x86
All
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 264683

People

(Reporter: volkmar, Assigned: bugzilla)

References

()

Details

(Keywords: crash, regression)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0 Firefox crashes when using Typeaheadfind. Reproducible: Always Steps to Reproduce: 1. Start Firefox from a clean profile 2. Customize Preferences, Advanced, Accessability Checkmark "Begin finding when you begin typing" 3. Visit page http://forums.mozillazine.org 4. Type "Buil" 5. Found and marked "Firefox Builds" 6. Hit ENTER button Actual Results: Crash Expected Results: Connect to http://forums.mozillazine.org/viewforum.php?f=23
Keywords: crash
Version: unspecified → 1.0 Branch
Second time trying to request "blocking-aviary1.0 ?" Didn't work first time.
Flags: blocking-aviary1.0?
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041017 Firefox/1.0 WFM hitting enter simply focussus the next item found
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0 It ONLY works for me when I start the search using a "/", but when I omit the slash and just start typing "buil" Firefix stops responding while trying to go to the active link. The expected behaviour (I think..) should be a continued search for the next occurence of "Buil" FF becomes completely unresponsive, but can be closed normally. The process however keeps running, so before restarting FF you have to end the process using Windows taskmanager. I'm using Windows Home edition, including SP2
I have accessibility.typeaheadfind false accessibility.typeaheadfind.autostart false and they seem to prevent me from getting into any trouble from all the FAYT bugs that are posted I can't reproduce a single one
Having a look at the filesize of that build which has increased by 52% from one day's build to the other's, I'm not so much surprised about mysterious behaviour (also Extemsion Manager is broken again and again when having a build with an abnormal filesize). ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2004-10-15-09-0.9/ -rwxrwxr-x 1 1004 7753 8553417 Oct 15 12:44 firefox-0.10.en-US.linux-i686.installer.tar.gz -rwxrwxr-x 1 1004 7753 8208277 Oct 15 12:47 firefox-0.10.en-US.linux-i686.tar.gz drwxrwxr-x 2 1004 7753 4096 Oct 15 12:45 linux-xpi ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2004-10-16-09-0.9/ -rwxrwxr-x 1 1004 7753 8567016 Oct 16 12:32 firefox-1.0.en-US.linux-i686.installer.tar.gz -rwxrwxr-x 1 1004 7753 12511138 Oct 16 12:35 firefox-1.0.en-US.linux-i686.tar.gz drwxrwxr-x 2 1004 7753 4096 Oct 16 12:34 linux-xpi Did somebody try the installer build?
I can reproduce this bug, but only under certain circumstances. 1) The selected text must be a hyperlink. 2) The crash is initiated by typing with accessibility.typeaheadfind set to true or typing ' to activate links only find as you type and then pressing enter on a selected link. Using the findbar or / seems to work fine. Oct. 16 Windows Installer build.
I can reproduce this on Windows also. - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041017 Firefox/1.0 - Fresh install, no extensions - Windows XP Pro
Changing to "All".
OS: Linux → All
firefox crashed right after I hit Enter to follow a found (focused) link. http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=1359250 no symbols in that stack trace, though. :-\
Keywords: regression
I'm pretty sure this is just a dup of the bug dbaron owns. *** This bug has been marked as a duplicate of 264683 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
are you sure this is a dup? the page I tested on was http://bugzilla.mozilla.org, which has neither plugin content nor popup windows.
Flags: blocking-aviary1.0?
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.