You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Juergen Donnerstag <ju...@gmail.com> on 2011/05/08 14:28:35 UTC
Eclipse running out-of-memory
Hi,
since recently my default eclipse installation runs out-of-memory when
running all core tests in debug mode. In run mode it doesn't. I know I
can extend the available memory, I just wonder what test (or recent
change) causes that mem demand. Using visualvm's basic mem profiling
features indicates that mem demand seems to double/triple all by a
sudden. Before installing yourkit (or any other profiler), I wonder if
somebody knows about it already. Because than I would increase my mem
setting. If it's a bug, than we should investigate,
-Juergen
Re: Eclipse running out-of-memory
Posted by Martin Grigorov <mg...@apache.org>.
Hi Juergen,
I debugged the tests quickly and I found these tests as thread-heavy:
org.apache.wicket.protocol.http.WicketFilterTest.testParallelCheckRedirect(int)
This method creates 8000 threads.
org.apache.wicket.pageStore.PageAccessSynchronizerTest
org.apache.wicket.page.persistent.disk.DiskDataStoreTest.test1()
creates a PageSavingThread
org.apache.wicket.versioning.PageVersioningTest.setup()
creates a PageSavingThread
All of them seems to clean properly after themselves.
I noticed only ModificationWatcher threads staying around. So I
disabled ModificationWatcher with r1102196 (WICKET-3703) and now it
should be better.
It seems that now all tests pass 30 secs faster on my machine
(2:40mins -> 2:12mins).
On Thu, May 12, 2011 at 8:57 AM, Juergen Donnerstag
<ju...@gmail.com> wrote:
> By now I also tested eclipse 3.7 M7 and several more combinations of
> jre's for eclipse and test itself. I also installed yourkit to dig a
> bit deeper. The problem remains irrespective of the jvm or eclipse.
>
> Using yourkit for testing I became aware that at the moment mem
> consumption increases, also the number of threads goes up. In case
> thread names are indication, than more than 8200 threads are created
> and destroyed during the test (with ModificationWatcher already
> disabled). However not all threads are destroyed. 150+ remain in
> memory (mostly waiting). Next step will be to figure out which data
> are attached to each thread to check if they cause the high demand for
> memory. Has any test or core source code been added or modified
> recently somehow related to this phenomen?
>
> -Juergen
>
> On Sun, May 8, 2011 at 10:11 PM, Martin Grigorov <mg...@apache.org> wrote:
>> I also can run the tests in debug mode (ubuntu, 64bit, 6GB RAM - not
>> sure what is the calculated -Xmx).
>> But since Juergen ran them successfully before and now they fail then
>> there could be something.
>> I work with one of the Tomcat committers in my current project and he
>> is preparing load tests for the app. If we find something in Wicket's
>> code I'll let you know.
>>
>> On Sun, May 8, 2011 at 9:57 PM, andrea del bene <an...@libero.it> wrote:
>>> Which is the amount of RAM on your XP pc? Anyway, it wouldn't be the first
>>> time I see memory management problems on Windows XP :-) :-). Can you run
>>> these tests on a different o.s.?
>>>>
>>>> I'm using XP. I installed Yourkit and ran the tests (1205) => no
>>>> problems. Only running standard eclipse (3.6) debug runs out of mem.
>>>>
>>>> - Juergen
>>>>
>>>> On Sun, May 8, 2011 at 9:11 PM, andrea del bene<an...@libero.it>
>>>> wrote:
>>>>>
>>>>> I've run them (1188 tests) twice in debug mode without any problem, under
>>>>> Ubuntu 10.10 64 bit and with 8 GB of ram.
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> since recently my default eclipse installation runs out-of-memory when
>>>>>> running all core tests in debug mode. In run mode it doesn't. I know I
>>>>>> can extend the available memory, I just wonder what test (or recent
>>>>>> change) causes that mem demand. Using visualvm's basic mem profiling
>>>>>> features indicates that mem demand seems to double/triple all by a
>>>>>> sudden. Before installing yourkit (or any other profiler), I wonder if
>>>>>> somebody knows about it already. Because than I would increase my mem
>>>>>> setting. If it's a bug, than we should investigate,
>>>>>>
>>>>>> -Juergen
>>>>>>
>>>>>
>>>
>>>
>>
>>
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
>>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: Eclipse running out-of-memory
Posted by Juergen Donnerstag <ju...@gmail.com>.
By now I also tested eclipse 3.7 M7 and several more combinations of
jre's for eclipse and test itself. I also installed yourkit to dig a
bit deeper. The problem remains irrespective of the jvm or eclipse.
Using yourkit for testing I became aware that at the moment mem
consumption increases, also the number of threads goes up. In case
thread names are indication, than more than 8200 threads are created
and destroyed during the test (with ModificationWatcher already
disabled). However not all threads are destroyed. 150+ remain in
memory (mostly waiting). Next step will be to figure out which data
are attached to each thread to check if they cause the high demand for
memory. Has any test or core source code been added or modified
recently somehow related to this phenomen?
-Juergen
On Sun, May 8, 2011 at 10:11 PM, Martin Grigorov <mg...@apache.org> wrote:
> I also can run the tests in debug mode (ubuntu, 64bit, 6GB RAM - not
> sure what is the calculated -Xmx).
> But since Juergen ran them successfully before and now they fail then
> there could be something.
> I work with one of the Tomcat committers in my current project and he
> is preparing load tests for the app. If we find something in Wicket's
> code I'll let you know.
>
> On Sun, May 8, 2011 at 9:57 PM, andrea del bene <an...@libero.it> wrote:
>> Which is the amount of RAM on your XP pc? Anyway, it wouldn't be the first
>> time I see memory management problems on Windows XP :-) :-). Can you run
>> these tests on a different o.s.?
>>>
>>> I'm using XP. I installed Yourkit and ran the tests (1205) => no
>>> problems. Only running standard eclipse (3.6) debug runs out of mem.
>>>
>>> - Juergen
>>>
>>> On Sun, May 8, 2011 at 9:11 PM, andrea del bene<an...@libero.it>
>>> wrote:
>>>>
>>>> I've run them (1188 tests) twice in debug mode without any problem, under
>>>> Ubuntu 10.10 64 bit and with 8 GB of ram.
>>>>>
>>>>> Hi,
>>>>>
>>>>> since recently my default eclipse installation runs out-of-memory when
>>>>> running all core tests in debug mode. In run mode it doesn't. I know I
>>>>> can extend the available memory, I just wonder what test (or recent
>>>>> change) causes that mem demand. Using visualvm's basic mem profiling
>>>>> features indicates that mem demand seems to double/triple all by a
>>>>> sudden. Before installing yourkit (or any other profiler), I wonder if
>>>>> somebody knows about it already. Because than I would increase my mem
>>>>> setting. If it's a bug, than we should investigate,
>>>>>
>>>>> -Juergen
>>>>>
>>>>
>>
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
Re: Eclipse running out-of-memory
Posted by Martin Grigorov <mg...@apache.org>.
I also can run the tests in debug mode (ubuntu, 64bit, 6GB RAM - not
sure what is the calculated -Xmx).
But since Juergen ran them successfully before and now they fail then
there could be something.
I work with one of the Tomcat committers in my current project and he
is preparing load tests for the app. If we find something in Wicket's
code I'll let you know.
On Sun, May 8, 2011 at 9:57 PM, andrea del bene <an...@libero.it> wrote:
> Which is the amount of RAM on your XP pc? Anyway, it wouldn't be the first
> time I see memory management problems on Windows XP :-) :-). Can you run
> these tests on a different o.s.?
>>
>> I'm using XP. I installed Yourkit and ran the tests (1205) => no
>> problems. Only running standard eclipse (3.6) debug runs out of mem.
>>
>> - Juergen
>>
>> On Sun, May 8, 2011 at 9:11 PM, andrea del bene<an...@libero.it>
>> wrote:
>>>
>>> I've run them (1188 tests) twice in debug mode without any problem, under
>>> Ubuntu 10.10 64 bit and with 8 GB of ram.
>>>>
>>>> Hi,
>>>>
>>>> since recently my default eclipse installation runs out-of-memory when
>>>> running all core tests in debug mode. In run mode it doesn't. I know I
>>>> can extend the available memory, I just wonder what test (or recent
>>>> change) causes that mem demand. Using visualvm's basic mem profiling
>>>> features indicates that mem demand seems to double/triple all by a
>>>> sudden. Before installing yourkit (or any other profiler), I wonder if
>>>> somebody knows about it already. Because than I would increase my mem
>>>> setting. If it's a bug, than we should investigate,
>>>>
>>>> -Juergen
>>>>
>>>
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: Eclipse running out-of-memory
Posted by andrea del bene <an...@libero.it>.
Which is the amount of RAM on your XP pc? Anyway, it wouldn't be the
first time I see memory management problems on Windows XP :-) :-). Can
you run these tests on a different o.s.?
> I'm using XP. I installed Yourkit and ran the tests (1205) => no
> problems. Only running standard eclipse (3.6) debug runs out of mem.
>
> - Juergen
>
> On Sun, May 8, 2011 at 9:11 PM, andrea del bene<an...@libero.it> wrote:
>> I've run them (1188 tests) twice in debug mode without any problem, under
>> Ubuntu 10.10 64 bit and with 8 GB of ram.
>>> Hi,
>>>
>>> since recently my default eclipse installation runs out-of-memory when
>>> running all core tests in debug mode. In run mode it doesn't. I know I
>>> can extend the available memory, I just wonder what test (or recent
>>> change) causes that mem demand. Using visualvm's basic mem profiling
>>> features indicates that mem demand seems to double/triple all by a
>>> sudden. Before installing yourkit (or any other profiler), I wonder if
>>> somebody knows about it already. Because than I would increase my mem
>>> setting. If it's a bug, than we should investigate,
>>>
>>> -Juergen
>>>
>>
Re: Eclipse running out-of-memory
Posted by Juergen Donnerstag <ju...@gmail.com>.
I'm using XP. I installed Yourkit and ran the tests (1205) => no
problems. Only running standard eclipse (3.6) debug runs out of mem.
- Juergen
On Sun, May 8, 2011 at 9:11 PM, andrea del bene <an...@libero.it> wrote:
> I've run them (1188 tests) twice in debug mode without any problem, under
> Ubuntu 10.10 64 bit and with 8 GB of ram.
>>
>> Hi,
>>
>> since recently my default eclipse installation runs out-of-memory when
>> running all core tests in debug mode. In run mode it doesn't. I know I
>> can extend the available memory, I just wonder what test (or recent
>> change) causes that mem demand. Using visualvm's basic mem profiling
>> features indicates that mem demand seems to double/triple all by a
>> sudden. Before installing yourkit (or any other profiler), I wonder if
>> somebody knows about it already. Because than I would increase my mem
>> setting. If it's a bug, than we should investigate,
>>
>> -Juergen
>>
>
>
Re: Eclipse running out-of-memory
Posted by andrea del bene <an...@libero.it>.
I've run them (1188 tests) twice in debug mode without any problem,
under Ubuntu 10.10 64 bit and with 8 GB of ram.
> Hi,
>
> since recently my default eclipse installation runs out-of-memory when
> running all core tests in debug mode. In run mode it doesn't. I know I
> can extend the available memory, I just wonder what test (or recent
> change) causes that mem demand. Using visualvm's basic mem profiling
> features indicates that mem demand seems to double/triple all by a
> sudden. Before installing yourkit (or any other profiler), I wonder if
> somebody knows about it already. Because than I would increase my mem
> setting. If it's a bug, than we should investigate,
>
> -Juergen
>
Re: Eclipse running out-of-memory
Posted by Martin Grigorov <mg...@apache.org>.
I didn't notice any change that would cause that.
I don't run the tests in debug mode but I always run my app in debug
mode (I work against 1.5-SNAPSHOT) and I didn't have any problems so
far.
On Sun, May 8, 2011 at 2:28 PM, Juergen Donnerstag
<ju...@gmail.com> wrote:
> Hi,
>
> since recently my default eclipse installation runs out-of-memory when
> running all core tests in debug mode. In run mode it doesn't. I know I
> can extend the available memory, I just wonder what test (or recent
> change) causes that mem demand. Using visualvm's basic mem profiling
> features indicates that mem demand seems to double/triple all by a
> sudden. Before installing yourkit (or any other profiler), I wonder if
> somebody knows about it already. Because than I would increase my mem
> setting. If it's a bug, than we should investigate,
>
> -Juergen
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com