[
https://issues.redhat.com/browse/WFLY-13514?page=com.atlassian.jira.plugi...
]
Flavia Rainone commented on WFLY-13514:
---------------------------------------
This is probably related to
https://github.com/undertow-io/undertow/commit/439001a0ca1fb4b0f44d63b06a... /
UNDERTOW-1573.
We do have a related discussion on this PR:
https://github.com/undertow-io/undertow/pull/862
I'll try reverting the PR and and running the reproducer to validate if it is really
the case. It is on my TODO list to investigate, as I mentioned in the PR above, a possible
solution to this. Given it affects other scenarios such as JSF + CDI beans, I'll be
investigating this next thing on my list.
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)