search

emnadridi / gmaps4jsf

Automatically exported from code.google.com/p/gmaps4jsf
0 stars 0 forks source link

gmap4jsf + <a4j:push> = ¿Memory leak? #86

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
See the example
http://mashups.s43.eatj.com/gmaps4jsf-push/index.jsf

Take a look to the memory usage by the web explorer in the task manager 
window.
The memory grows with the time.

I think there is a problem with the memory management.

¿Any solution?
Thanks.
Version gmap4jsf-1.1.2-SNAPSHOT

Original issue reported on code.google.com by elpa...@gmail.com on 17 Nov 2009 at 3:43

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I think it is a problem of <a4j:push>.
Do you have more details about the problem description?

Original comment by Hazem.sa...@gmail.com on 18 Nov 2009 at 8:59

GoogleCodeExporter commented 9 years ago 
First, excuse me for my english and for my knowledge.
I want to refresh <m:map> component with a dynamic collection of markers (try 
with 
100 or more to see the memory consumption), then I have decided to use 
<a4j:push> 
like the example
http://mashups.s43.eatj.com/gmaps4jsf-push/index.jsf.
Then I have noticed that every time the map component is rerendered the memory 
used 
by the web explorer(firefox,chrome, iexplorer) increases.
However I need that this refresh remain for some hours, but this takes to run 
out of 
memory.
I have tried to use <body onunload="GUnload()">, but it hasn´t changed 
anything.

¿Perhaps the solution is not to rerender the map component, and repaint the 
markers 
throug jsvariable and maps api?

I am trying to find out how to solve this particular situation.

I don't know if the problem is really the <m:map> component, the memory policy 
of the  
web explorer, or the <a4j:push> component.

Any solution for this problem will be welcome.
Thanks.

Original comment by elpa...@gmail.com on 19 Nov 2009 at 9:16

GoogleCodeExporter commented 9 years ago 
This should not be the problem of the map component as it re-renders for every 
push.

Original comment by Hazem.sa...@gmail.com on 24 Nov 2009 at 10:28

GoogleCodeExporter commented 9 years ago

Original comment by Hazem.sa...@gmail.com on 24 Feb 2010 at 11:25