407337 - Memory leak after opening ajax-connection with a page on localhost with a bug that makes apache crash.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Wander]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

I used an xmlhttp request(ajax) to recieve data from a page that I made in php. There was a bug in the php script that made my apache-server crash. After restarting apache the memory of firefox still kept going up.

Reproducible: Always

Steps to Reproduce:
1. Open the page that I made (You can mail me if you want the source code if i don't manage to include it as an attachment on the next page)
2. Press the button to open the ajax-connection
3. Wait till the server crashes (or close it using task manager)
Actual Results:  
The memory of firefox kept going up (50mb, 60mb, 70mb ... 200mb..)

Expected Results:  
Act normal?

I'm using Apache 2.2 with PHP 5.2.3

Comment 1

[Wander]

Attachment: This is the source code of the page that makes the server crash which causes a memory leak in firefox.

Comment 2

[Jesse Ruderman on Windows]

Wander, does this still cause a leak in Firefox 3.5?

Comment 3

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.