[
https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s...
]
Juraj Húska edited comment on RF-13250 at 2/20/14 10:47 AM:
------------------------------------------------------------
I can confirm that the patch is fixing the issue. There are no memory issues when running
the tests with application in {{javax.faces.ProjectStage = PRODUCTION}}. When the mode is
{{DEVELOPMENT}} then the issue still persists even when the patch is used. But I guess
that it ok. Right, [~lfryc] ?
For now I have reproduced the issue for RichFaces 5-SNAPSHOT and same for the fix. But I
guess that it will be the same for all the other RF versions (AFAIK the affected class is
same in all version). However, I am gonna try.
was (Author: jhuska):
I can confirm that the patch is fixing the issue. There are no memory issues when
running the tests with application in {{javax.faces.ProjectStage = PRODUCTION}}. When the
mode is {{DEVELOPMENT}} then the issue still persists even when the patch is used. But I
guess that it is right ? [~lfryc]
For now I have reproduced the issue for RichFaces 5-SNAPSHOT and same for the fix. But I
guess that it will be the same for all the other RF versions (AFAIK the affected class is
same in all version). However, I am gonna try.
Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
--------------------------------------------------------------
Key: RF-13250
URL:
https://issues.jboss.org/browse/RF-13250
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.3.4, 4.3.5
Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14,
RichFaces 4.3.4, APR 1.4.5
Reporter: Milo van der Zee
Assignee: Juraj Húska
Labels: memoryleak
Attachments: rf.patch
Hello,
I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash
with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the
problem is gone.
I also started seeing this message lot's of times:
{{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
I don't know if that has anything to do with the error. I set
{{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But
still the application went out-of-memory.
In the crashed system heap dump I see a lot of:
- AtomicBoolean (751.000, 15.0MB)
- ConcurrentLinkedQueue
- AtmospereRequest$Builder (60.042, 13.8MB)
To me it looks like it has something to do with Atmosphere. Any ideas?
Thanks,
Milo van der Zee
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira