ajax have memory leak in firefox and i.e.

Reported by:	roberto@spadim.com.br	Owned by:	roberto@spadim.com.br
Priority:	low	Milestone:	1.next
Component:	ajax	Version:	1.6.2
Keywords:		Cc:
Blocked by:		Blocking:

Description

i will send a php code, be sure that jquery-1.6.1.js is in the same directory....

start. after +- 6000 counter alert message the memory is about 60mb, at the start of firefox4 it was 30mb... any idea?

i will send code as link since askmetic is spanning my message

Attachments (0)

Change History (4)

Changed June 30, 2011 08:52PM UTC by anonymous comment:1


... php code at start of page:
	if($_REQUEST['frame']==1)
		die();
	
<html>
<head>
<script language="javascript" src="jquery-1.6.1.js"></script>
</head>
<body>
<script language='javascript'>
var contador=0;
function get_values(){
	jQuery.ajax({
			type: "GET",
			url:"bug.jquery.php",
			data:"frame=1",
			dataType:"text",
			cache:false,
			success:show_values
		});
}
function show_values(){
	contador++;
	if((contador % 2000)==0)
		alert(contador);
	get_values();
}
get_values();	// start loop...
</script>
</body>
</html>

Changed June 30, 2011 08:53PM UTC by anonymous comment:2

i think it´s near to this bug:

http://bugs.jquery.com/ticket/6242

Changed June 30, 2011 09:22PM UTC by timmywil comment:3

component:	unfiled → ajax
owner:	→ roberto@spadim.com.br
priority:	undecided → low
status:	new → pending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on http://jsfiddle.net that reproduces the issue experienced to help us assess your ticket.

Additionally, test against the jQuery (edge) version to ensure the issue still exists.

Changed July 15, 2011 08:04AM UTC by trac-o-bot comment:4

resolution:	→ invalid
status:	pending → closed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Side navigation