[weld-issues] [JBoss JIRA] Commented: (WELD-711) Calling Contextual.destroy on an instance still references an instance on BeanManager

[Martin Gencur (JIRA)]

    [ https://issues.jboss.org/browse/WELD-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568938#comment-12568938 ] 

Martin Gencur commented on WELD-711:
------------------------------------

I just found out that the commit slowed it down but not that much as I wrote. The previous commits between the 2 mentioned commits caused even bigger slowdown. I will try to find where the problem is (in which commit).

> 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