First scenario cause leak for exactly one instance of ignite. Second scenario cause leak for one instance per distinct key in thread local map (if key is ignite name, as much distinct names used in test, so much links leaked, I don’t know what is key in that map =() . Ways to GC root in original letter I got using JVisualVM on heap dump I take after following commands: Ignition.stopAll(true); TestUtils.pause(5000); //wait for relaxation System.gc(); TestUtils.pause(1000); //wait for relaxation System.gc(); TestUtils.pause(1000); //wait for relaxation System.gc(); TestUtils.pause(1000); //wait for relaxation System.gc(); TestUtils.pause(1000); //wait for relaxation Andrey. От: Ilya Kasnacheev Hello! Our test suites start tens of thousands nodes during every suite run. If there would be any leaks in start-stop scenario, we would surely notice this. I recommend checking why this is a problem in your scenario. The problem you have mentioned may cause problems with class de-loading, however. Do you bring a new class loader for each test? Can you file an issue about this so that we code a proper de-allocation? Regards, -- Ilya Kasnacheev ср, 18 мар. 2020 г. в 18:37, Andrey Davydov <andrey.davy...@gmail.com>:
|
- Ignite memory leaks in 2.8.0 Andrey Davydov
- Re: Ignite memory leaks in 2.8.0 Ilya Kasnacheev
- Re: Ignite memory leaks in 2.8.0 Ilya Kasnacheev
- RE: Re: Ignite memory leaks in 2.8.0 Andrey Davydov
- RE: Ignite memory leaks in 2.8.0 Andrey Davydov
- Re: Ignite memory leaks in 2.8.0 Andrey Davydov
- Re: Ignite memory leaks in 2.8.0 Taras Ledkov
- Re: Ignite memory leaks in 2.8.0 Andrey Davydov
- Re: Ignite memory leaks in 2.8.0 Taras Ledkov
- RE: Re: Ignite memory leaks in 2.8.0 Andrey Davydov
- Re: Ignite memory leaks in 2.8.0 Ilya Kasnacheev
- RE: Re: Ignite memory leaks in 2.8.0 Andrey Davydov