Tracking bug:
http://code.google.com/p/google-web-toolkit/issues/detail?id=7648
On Tuesday, August 28, 2012 7:13:27 PM UTC-7, Brian Slesinsky wrote:
Reproduced the thread leak in the Firefox 15 release that I'm working on.
(On a Mac; using jps to list the threads.)
On Tuesday, August 28,
I analyzed this a bit more (this time on Linux), and I noticed, that the
number of Thread also grows: 1 thread per reload. Again, this happens only
with Firefox, not with Chrome. So probably the ClassLoader references will
be discarded only when the Thread terminates...
One more thing that
In other words: it looks like the Firefox plugin doesn't send a QuitMessage
to the DevMode, and worse, is kept alive in the background!
On Tuesday, August 28, 2012 11:05:38 AM UTC+2, Chris Lercher wrote:
I analyzed this a bit more (this time on Linux), and I noticed, that the
number of
Thanks, I think I can do something about this.
On Tue, Aug 28, 2012 at 2:15 AM, Thomas Broyer t.bro...@gmail.com wrote:
In other words: it looks like the Firefox plugin doesn't send a QuitMessage
to the DevMode, and worse, is kept alive in the background!
On Tuesday, August 28, 2012 11:05:38
Does the connection leak happen with all plugins (other than GWT) disabled?
On Tuesday, August 28, 2012 7:57:37 AM UTC-7, Brian Slesinsky wrote:
Thanks, I think I can do something about this.
On Tue, Aug 28, 2012 at 2:15 AM, Thomas Broyer wrote:
In other words: it looks like the Firefox
Yes. I disabled all Add-Ons: All Extensions (except for the GWT Extension)
and all Plugins, and restarted Firefox.
On Wednesday, August 29, 2012 12:12:03 AM UTC+2, Brian Slesinsky wrote:
Does the connection leak happen with all plugins (other than GWT) disabled?
--
You received this
Reproduced the thread leak in the Firefox 15 release that I'm working on.
(On a Mac; using jps to list the threads.)
On Tuesday, August 28, 2012 3:31:10 PM UTC-7, Chris Lercher wrote:
Yes. I disabled all Add-Ons: All Extensions (except for the GWT Extension)
and all Plugins, and restarted
When I analyze a DevMode process's memory usage (e.g. using jconsole), it
shows that Heap and Non-Heap (PermGen) Memory usage increases, whenever the
page is reloaded.
This happens both when I run DevMode with Firefox 14, as well as Chrome 21.
The difference is however, that
- with Chrome,
That's an interesting report. We always want to garbage collect the
ClassLoader when the session is over and if that doesn't happen, it's a
bug. I don't know why Firefox would behave differently; the JVM side should
work the same way for Firefox versus Chrome. The only thing I can think of
is
