Stops responding when replying to a thread or using "quote" to reply to a thread

RESOLVED EXPIRED

Status

()

Firefox
General
--
major
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: Craig Douglas, Assigned: Blake Ross)

Tracking

({hang})

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: 

I have just installed Firefox, it is very smooth, however, when I use it on www.wilderssecurity.com (registered member) to look at a thread, if I try to reply, Firefox stops responding and my CPU usage climbs to approx 51%. 

I'm running stock standard 0.9.2 it locks the page, I can Control+Alt+Delete and close the "not responding" pages. This is only found when replying to a post or using quote to reply to a post. I tried rebooting to no avail. Then tried IE and everything is normal, only find problem with Firefox...

Reproducible: Always
Steps to Reproduce:
1. As described above, go to Wilders Security
2. View a thread
3. try to reply or use "quote" to reply

Actual Results:  
Page stops responding

Expected Results:  
Continued, allowing a reply or a quote and a reply.

Updated

14 years ago
Assignee: bugs → firefox
Severity: normal → major
Component: Web Site → General
Keywords: hang
QA Contact: firefox.general
(Reporter)

Comment 1

14 years ago
Solution was found, see:

http://www.wilderssecurity.com/showthread.php?t=41946

after removing and reinstalling to no avail, I was advised to remove the 
Mozilla folder from Documents and Settings\User\Application Data, restart FF, 
it then asked if I wanted to "Import" settings, I said no, and now it's as it 
should be...

Comment 2

14 years ago
I have the same problem, FireFox appears to be parsing the tags in the textarea,
I have 2 links that demonstrate the problem.

I run a forum, and for message preview I need to prefill the textarea from a
previous copy, users who enter for example an img tag, but miss off the closing
quote around the URL are currently corrupting the next page.

http://www.nigelbrooks.com/textarea1.html
- this file has an unmatched " inside the textarea, FireFox missed the
</textarea> tag, and include extra code in the edit box.

http://www.nigelbrooks.com/textarea1.html
- I tried using &quot; (&amp;quot; - in case this is parsed here) to get around
this, which half works, at least it sees the </textarea> tag, but inside tags
within the textarea, &quot; (&amp;quot; - in case this is parsed here)is NOT
converted to " (it is outside any other tags)

The pages give more details. BOTH versions work fine with IE (6) and NetScape
4.76, I've not tried with anything else...

Nigel Brooks

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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.