Comment by pclog...@gmail.com:
The best poker blog http://poker-blogs-see.blogspot.com
Best PokerStars blog http://pokerstars-blogs.blogspot.com
Sexy, hot girls imagehttp://china-sexy-girl-images.blogspot.com/
For more information:
Comment by j...@google.com:
@bob.whiton: I'm assuming you mean something like this:
B.addFooHandler(A);
// drop reference to A
This is just normal Java memory management -- nothing magic. So if B is
still around (because it is, e.g., a widget still attached to the
document), then A will
Comment by bob.whiton:
I have a question regarding the com.google.gwt.event.shared.HandlerManager
and memory leaks. Let's say that Object A calls addHandler on Object B
which contains an instance of HandlerManager. If I destroy Object A, will
Object B still have a reference to it? I
Comment by atul.dambalkar:
We also have quite a big GWT based application. In our application, we have
also seen similar memory issues showing up in FireFox3.6, IE and Chrome4.1
as well. Browsers eventually stopped responding (with CPU more than 70%)
after memory reaching up to 1GB
Comment by j...@google.com:
I'm not aware of any way on most browsers to force a GC. On IE, there's the
global CollectGarbage() function, but IE already runs GC too frequently
most of the time anyway, so it's not much help. I'm less familiar with
Firefox and Safari, but Chrome's GC is
Comment by GlacieredPyro:
Thanks for the response,
I see now that only by running IE in no addon mode will stop the memory
from growing, in fact it doesnt get near 30MB.
Not that my normal IE installation has anything but the default addons but
they seem to make the most trivial application
Comment by j...@google.com:
I've run through this with IE7, IE8, Microsoft's IE JS Leak Detector, and
Chrome, and I'm not seeing any evidence of it leaking, on IE at least. On
my Vista box, memory grows steadily as I add more items, then mostly
recovers as I clear or reset. There is a
Comment by GlacieredPyro:
I'm sitting with a situation where either my code is horribly bad and I
should not be in the development industry or there is something wrong.
The following short code sample will leak. In IE 7/8 the odds of getting
memory back are slim to none. FF2 gives some
Comment by micahherstand:
If I have classes in Java that reference each other, is this considered
circular referencing and therefore will they never be GC'd? I'm having
big-time memory leaks in FF and Safari without JSNI.
Very stripped down example:
{{{
class Controller{
Model m;
