For Java, your main concern is not about memory leak (with the exception of objects added in some custom containers)... you need to worry more on other kind of resources like connections and mutexes.
Using Thread to re-run the application
Using Thread to re-run the application
|
|
Feb 6 2006, 06:17 PM
Return to original view | Post
#1
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
4,464 posts Joined: Jan 2003 |
For Java, your main concern is not about memory leak (with the exception of objects added in some custom containers)... you need to worry more on other kind of resources like connections and mutexes.
|
|
|
Feb 8 2006, 06:51 PM
Return to original view | Post
#2
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
4,464 posts Joined: Jan 2003 |
GC based program, it is hard to notice a pattern that denotes a memory leak. GC sweeping are indeterministic. It might go up for sometime and suddenly the program jerk a little, and memory usage is back to normal.
|
| Change to: | 0.0140sec
1.62
6 queries
GZIP Disabled
Time is now: 23rd December 2025 - 08:19 AM |