Hi! I'm developing a chrome extension and I tried hard all the solutions in the web but no one seems to work. My jsscript only consume an html (about 13,30k per request) via XMLHttpReq(XHR) and parse the response , dropping everything that no match with some regex. All this happen with a setTimeout inside in the XHR onload method and seems to work but the problem comes after 10minutes aprox. when I saw what happens in memory. After 10minutes the extensions mem grows from 10mb to 60. So ..what happens and exist any kind of solution to this? I read that is a normal grow because its a new request and the Garbage Collector runs after a while (so late) but for my its another thing. Thanks in advance and SORRY FOR MY BAD ENGLISH.
Java Pal - Your friend in technology and innovation...India.
What I mean with memory growing is that mem increased gradually across extension's live.
I modified my algorithm (using JQuery) for a proof concept without the parse part , assuming that the problem was in there and not in XHR. But same result , mem still grows incrementally forever.
So I suspect that XHR hold memory and GC never release all the stack (I run manually GC from Developer Tools , from 60mb down to 50mb when gc run) and I never saw GC running naturally (triggered by Chrome) . I will test this in a virtual with low mem so i can see what happens.