[Issue 3692] New - FATAL: Java heap space

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[Issue 3692] New - FATAL: Java heap space

drewyaus
https://hudson.dev.java.net/issues/show_bug.cgi?id=3692
                 Issue #|3692
                 Summary|FATAL: Java heap space
               Component|hudson
                 Version|current
                Platform|All
              OS/Version|Linux
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|crap4j
             Assigned to|dlindner
             Reported by|drewyaus






------- Additional comments from [hidden email] Fri May 15 14:16:35 +0000 2009 -------
We seem to be having troubles with heap space and the plugin.

[CRAP4J] Collecting Crap4J analysis files...
[CRAP4J] Searching for report files within checkout/_DIST/reports/crap/report.xml
[CRAP4J] Using the new FileSetBuilder
FATAL: Java heap space
java.lang.OutOfMemoryError: Java heap space

Crap itself seems to be finishing, but the plugin is doing something to use up
heap space. It's intermittent, of course. We can increase heap size for the
build process, but I thought I'd ask here for alternative ideas.

thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 3692] FATAL: Java heap space

dlindner
https://hudson.dev.java.net/issues/show_bug.cgi?id=3692



User dlindner changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |STARTED
--------------------------------------------------------------------------------




------- Additional comments from [hidden email] Mon May 18 20:49:37 +0000 2009 -------
Hi drewyaus,

thank you for this issue. As there is a workaround (throw more memory on it), i
think its not a high pressure issue.

The Crap4J plugin uses an internal data model that is stored in memory. I think
i can improve the deconstruction of the model once data isn't used anymore.
Right now, the model gets completly built and processed only afterwards.

Just to have a guideline of your memory consumption: how many classes/methods
are in your report.xml? Is the plugin working on a 64bit JVM? How much memory
was (or might have been) allocated before the OOME?



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 3692] FATAL: Java heap space

drewyaus
In reply to this post by drewyaus
https://hudson.dev.java.net/issues/show_bug.cgi?id=3692






------- Additional comments from [hidden email] Tue May 19 07:45:08 +0000 2009 -------
Thanks for response.  We have a lot of applications in Hudson, so i wanted to
check before we start upping the memory for all of them.

We have 8203 methods. Not sure how many classes. JVM runs in 32bit mode. We
don't specify any memory options, so it must be the default for our build server
(x86_64 GNU/Linux).

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 3692] FATAL: Java heap space

dlindner
In reply to this post by drewyaus
https://hudson.dev.java.net/issues/show_bug.cgi?id=3692






------- Additional comments from [hidden email] Sun Jul  5 19:37:06 +0000 2009 -------
Hi drewyaus,

i worked on this issue a bit and was able to lower the memory consumption. The
layer that reads the crap4j data was written as a generic API, but most of its
functionality isn't used within the crap4j plugin. After disabling it, there is
no more wasted memory.

I will append a preview version of the plugin that is under testing right now.
If you don't mind to add your testing expertise, you're welcome.
I haven't done memory benchmarks yet.

Side note:
If you wonder what other tools are using this API, have a look at the crapmap.
http://schneide.wordpress.com/2009/06/15/a-guide-through-the-swamp-the-crapmap/



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 3692] FATAL: Java heap space

dlindner
In reply to this post by drewyaus
https://hudson.dev.java.net/issues/show_bug.cgi?id=3692






------- Additional comments from [hidden email] Sun Jul  5 19:38:36 +0000 2009 -------
Created an attachment (id=771)
version 0.7-SNAPSHOT of crap4j plugin. lower memory footprint


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]