What puzzles me especially about this:
there should be no old data from the plugin: I have only released a single version of the plugin!
Gesendet: Dienstag, 08. Oktober 2013 um 14:37 Uhr
Von: "Vojtech Juranek" <[email protected]>
An: [email protected]
Betreff: Re: Aw: memory leak in jenkins?
Von: "Vojtech Juranek" <[email protected]>
An: [email protected]
Betreff: Re: Aw: memory leak in jenkins?
On Tuesday 08 October 2013 14:11:01 Christoph Kutzinski wrote:
> Caan you open a JIRA issue against the plugin?
while this could be fixed by changes in plugin (probably by fixing backward
compatibility), the root cause seems to be Old data monitor which keeps all
old data in memory, which can quite easily cause OOM. Even worse, it *may*
happen that Old data monitor automatically turn on even if it was manually
turned off before. I observed it on one of our Jenkins instance where OOM
happened quite often because of Old data monitor, but haven't had enough time
to investigate it yet.
@Ohad - quick fix could be disable Old data monitor and turn it on once plugin
is fixed. You can also check if it turn back on itself to confirm/disapprove my
observation above
> Caan you open a JIRA issue against the plugin?
while this could be fixed by changes in plugin (probably by fixing backward
compatibility), the root cause seems to be Old data monitor which keeps all
old data in memory, which can quite easily cause OOM. Even worse, it *may*
happen that Old data monitor automatically turn on even if it was manually
turned off before. I observed it on one of our Jenkins instance where OOM
happened quite often because of Old data monitor, but haven't had enough time
to investigate it yet.
@Ohad - quick fix could be disable Old data monitor and turn it on once plugin
is fixed. You can also check if it turn back on itself to confirm/disapprove my
observation above
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
