297633 - computer locks up while closing pdf file.

Status: RESOLVED EXPIRED

(Firefox :: File Handling, defect)

Description

[Gareth]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier:  Firefox/1.0.4

My config: 2.5 GHz P4 Notebook, 500M RAM, 700M pagefile.  WinXP 2000 + SP2
Acrobat 6 Full for editing pdf files + Acro 7 reader for viewing pdf wthin browser. 

Having read the FAQs & info on Firefox and Acro bat pages ( I hope all) I edited
Grepref/all.js to search for acro7 plugin  - OK finally. Having to do that may
count as a minor bug in itself, but moving on:

pdf files now load nicely into browser. WHEN YOU CLOSE THEM the computer freezes
& the hard drive starts spinning at max revs for up to a minute or until I force
FF to close with Task Manager. 

Reproducible: Sometimes

Steps to Reproduce:
1.Have a large number of tabs open, preferably with two or more windows
2.Open a pdf page
3.Close a pdf page

Problem is noticeable when simply closing a pdf page with nothing else open.

Actual Results:  
FF 104 hangs, swinging gently in the breeze. Hard drive appears determined to
achieve speed of sound, spinning at max revs for up to a minute. I then forced
FF to shut down with Windows task manager. At some point this has caused FF to
behave strangely: 
1.The default fonts change.   
2.Adblocker, which is turned off, consistently blocks some links:
http://www.qantas.com.au/fflyer/dyn/partners/wineClub then click 
http://www.qantaswineclub.com.au/
3. Some radio button options in Tools/Options have no selection made. eg
General/Connection Settings; Advanced/Tabbed Browsing/Open links from other
apllications in.. 

Expected Results:  
Gracefully closed the pdf page.

The problems with Adblocker and the new fonts can be fixed by creating a new FF
profile.

Comment 1

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

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.

Comment 3

[Gareth]

My apologies: This is actually a complete furphy. What had happened was this: 
While editing the user.js file in Wordpad in order to tune Firefox's use of the
Acrobat plugin I managed to add the word "Acrobat" to the beginning of the file.
 Removing that has caused FF to work beautifully ever since and I of course feel
like a complete idiot.