Geek Answers Handbook

Understanding RES memory in * nix and memory leak

RE: Possible error with releasing native memory in Java

It occurred to me that memory REScan display much more memory than what your application really allocated. In the above example, there are many alloc / dealloc commands, but the memory is RESstuck on a lot. I know that this is not the result of JIT or other memory processes, as you can usually allocate and dealloc 500M, and watch as they RESgo up and down in normal conditions.

jon@ubuntu-dev:~$ top -d 1 -p 31067 | grep java
 31067 jon       20   0 6847648  27988  15420 S   0.0  0.2   0:00.09 java       
 31067 jon       20   0 7769264 743952  15548 S 315.5  4.6   0:03.25 java       
 31067 jon       20   0 7900336 847868  15548 S 380.1  5.3   0:07.06 java       
 31067 jon       20   0 7834800 810324  15548 S 379.1  5.0   0:10.86 java       
 31067 jon       20   0 7703728 700028  15548 S 379.2  4.3   0:14.66 java       
 31067 jon       20   0 7900336 894940  15548 S 379.2  5.5   0:18.46 java       
 31067 jon       20   0 7703728 674400  15548 S 277.5  4.2   0:21.24 java       
 31067 jon       20   0 7376048 430868  15548 S  59.9  2.7   0:21.84 java       
 31067 jon       20   0 7376048 430868  15548 S   0.0  2.7   0:21.84 java       
 31067 jon       20   0 7376048 430868  15548 S   1.0  2.7   0:21.85 java       
 31067 jon       20   0 7376048 430868  15548 S   0.0  2.7   0:21.85 java       
 31067 jon       20   0 7376048 430868  15548 S   1.0  2.7   0:21.86 java

The app here does NOT hold on to so much memory. Java says the fixed size is 35 MB and the size of its own memory is 0.

, , ?

0
1

, "" ? , RES, , . , .

0

More articles:


All Articles