[jboss-jira] [JBoss JIRA] (WFLY-13514) Huge memory leak in WildFly
Matěj Novotný (Jira)
issues at jboss.org
Wed May 27 04:31:21 EDT 2020
[ https://issues.redhat.com/browse/WFLY-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117176#comment-14117176 ]
Matěj Novotný commented on WFLY-13514:
--------------------------------------
Thanks for reporting this, I'll take a look at this sometime this week.
Bean lifecycle should be bound to its context; once you tear down, say, request context, you destroy all its beans regardless of where they are. I suspect these could be proxies rather then beans that are hanging around.
> Huge memory leak in WildFly
> ---------------------------
>
> Key: WFLY-13514
> URL: https://issues.redhat.com/browse/WFLY-13514
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF
> Affects Versions: 18.0.1.Final, 19.1.0.Final, 20.0.0.Beta1
> Reporter: Konrad Bak
> Assignee: Matěj Novotný
> Priority: Critical
>
> https://github.com/konbk/bug-report-wildfly-oome
> The project shows a huge memory leak introduced in recent WildFly versions that can crash a real-world Java EE application in a matter of hours.
> When a JSF page contains any component bound to page variable, all CDI beans (regardless of scope) used on that page stay in memory.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list