https://bz.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #16 from Christopher Schultz ---
(In reply to Mark Thomas from comment #13)
> On reflection
I see what you did, there. ;)
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bz.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #15 from Mark Thomas ---
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8199589
--
You are receiving this mail because:
You are the assignee for the bug.
---
https://bz.apache.org/bugzilla/show_bug.cgi?id=51195
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
Hi Rory,
Just a quick heads up.
Anything you can do to get the enhancement request below in front of the
right folks would be appreciated.
Thanks,
Mark
On 13/03/18 14:29, bugzi...@apache.org wrote:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=51195
>
> --- Comment #13 from Mark Thomas -
https://bz.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #13 from Mark Thomas ---
On reflection, I don't think this is a JRE bug but an enhancement request. I
have submitted the RFE and been given ID 9052974.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #12 from Mark Thomas ---
I'd argue that this is a JRE bug. Given the possibility of a memory leak, a
method should be provided to enable the cache to be cleared for a given class
loader.
I'm working on extending https://github.com/
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
Larry G. Rapp changed:
What|Removed |Added
Attachment #29258|text/html |application/html
mime typ
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #11 from Larry G. Rapp ---
Created attachment 29258
--> https://issues.apache.org/bugzilla/attachment.cgi?id=29258&action=edit
test
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #10 from Konstantin Kolinko 2011-07-26
11:19:08 UTC ---
I think there might be additional options for the findleaks command.
E.g. make calling gc optional, or perform additional cleanup as described here.
--
Configure bugmai
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #9 from Sylvain Laurent 2011-05-24 20:17:19
UTC ---
just my 2cts : I'm leaning towards Joern point of view, that cleaning the
ObjectStreamClass cache should be done during the Find Leaks action rather than
when stopping the web
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #8 from Joern Huxhorn 2011-05-24 14:35:17
UTC ---
(In reply to comment #7)
> Joern,
> (In reply to comment #6)
> > The cleanup performed in the code is merely to prevent a *false* memory leak
> > warning. A real leak does, in f
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #7 from Christopher Schultz
2011-05-24 13:59:07 UTC ---
Joern,
(In reply to comment #6)
> The cleanup performed in the code is merely to prevent a *false* memory leak
> warning. A real leak does, in fact, not exist. This is the
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #6 from Joern Huxhorn 2011-05-24 11:09:57
UTC ---
I disagree.
The cleanup performed in the code is merely to prevent a *false* memory leak
warning. A real leak does, in fact, not exist. This is the reason why I put it
directly
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #5 from Mark Thomas 2011-05-20 18:58:43 UTC ---
A couple of comments on the proposed patch.
1. This looks like clean-up code and as such is better placed in the
WebappClassLoader as another ClearReferencesXXX method.
2. Rather
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #4 from Joern Huxhorn 2011-05-19 17:19:01
UTC ---
Created attachment 27038
--> https://issues.apache.org/bugzilla/attachment.cgi?id=27038
Implements the suggested change in StandardHost
This patch against trunk implements th
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #3 from Mark Thomas 2011-05-18 17:38:13 UTC ---
The code referenced above from logback is not licensed in a way that allows it
to be used in an ALv2 work in source form.
The gc leaks functionality already includes a warning tha
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #2 from Joern Huxhorn 2011-05-17 00:17:23
UTC ---
Calling System.gc() is not enough at all since the caches in question contain
SoftReferences that are not collected until the VM is running out of memory.
This is the root of th
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #1 from Christopher Schultz
2011-05-16 21:54:00 UTC ---
The patch as written seems a bit over-reaching, possibly non-threadsafe and
might even be JVM-specific.
It's over-reaching in that it purges the ObjectStreamClass's cache
https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
Konstantin Kolinko changed:
What|Removed |Added
OS/Version||All
Severity|normal
19 matches
Mail list logo
