[jboss-jira] [JBoss JIRA] (WFLY-13514) Huge memory leak in WildFly

[Konrad Bak (Jira)]

    [ https://issues.redhat.com/browse/WFLY-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118482#comment-14118482 ] 

Konrad Bak commented on WFLY-13514:
-----------------------------------

Thank you for your quick reaction!

{quote}
Konrad Bak funy thing is, I cannot reproduce this manually. If I just try and GET that page from browser (repeatedly OFC), it never goes OOM.
{quote}
Yeah, I was surprised as well. Because of that, the bug went unnoticed through our staging environment, and we experienced it only in production.

I am not sure if you noticed that the binding is crucial here. If we remove {{binding="#\{pageVariable\}"}}, the bug disappears.

> 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)