[
https://issues.jboss.org/browse/WELD-711?page=com.atlassian.jira.plugin.s...
]
Martin Gencur commented on WELD-711:
------------------------------------
Pete, I think the most effective way is to do a stress test for both of the new states
which are there now, it means weld/master: head=f8b0445fd and you branch: head=c3ee8a971
and if the difference is in the one commit - make jprofiler snapshots for both of these
states . Otherwise (since you've changed your branch) I would have to create my fork
of your branch and get it into the previous state which was tested. Agreed? I have to do
it sequentially.
Calling Contextual.destroy on an instance still references an
instance on BeanManager
-------------------------------------------------------------------------------------
Key: WELD-711
URL:
https://issues.jboss.org/browse/WELD-711
Project: Weld
Issue Type: Bug
Components: Scopes & Contexts
Affects Versions: 1.0.1.Final, 1.1.0.Beta1
Reporter: George Gastaldi
Assignee: Martin Gencur
Priority: Minor
Labels: AnnotationLiteral, MemoryLeak
Fix For: 1.1.0.CR1
Attachments: report.txt
Using the seam-faces module @ViewScoped extension, when the object is destroyed by
Contextual.destroy, weld still references an instance, avoiding being garbage-collected.
Pseudo Code:
Contextual contextual = ...
Object instance = ...
CreationalContext creational = ...
contextual.destroy(instance, creational);
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira