aspose file tools
The moose likes Other Open Source Projects and the fly likes JAMon - implications if Monitor#stop is never reached Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of Arduino in Action this week in the General Computing forum!

A special promo: Enter your blog post or vote on a blogger to be featured in an upcoming Journal
JavaRanch » Java Forums » Products » Other Open Source Projects
Reply Bookmark "JAMon - implications if Monitor#stop is never reached" Watch "JAMon - implications if Monitor#stop is never reached" New topic
Author

JAMon - implications if Monitor#stop is never reached

myyron latorilla
Greenhorn

Joined: Dec 10, 2009
Posts: 26
posted private message
0
Quote
Hi,

Not sure if this topic is on the right category, please do advise.

For the subject, I'm wondering what are the implications if Monitor#stop is never reached in the code. Thanks in advance.
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 35443
    
    9
posted
1
Quote
Depends on the amount of data you're tracking. You could run out of memory at some point.

Android apps – ImageJ plugins – Java web charts
steve souza
Ranch Hand

Joined: Jun 26, 2002
Posts: 852
posted private message
0
Quote
not calling 'stop' has no effect on memory in jamon. The only result is that the 'active' number will continually climb, but the objects themselves will be properly garbage collected when the code goes out of scope.

http://www.jamonapi.com/ - a fast, free open source performance tuning api.
JavaRanch Performance FAQ
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JAMon - implications if Monitor#stop is never reached
 
Similar Threads
Thought of the Day!
Clarify...while....
WA #1.....word association
In reference to notify maybe pausing a thread?
String Equality diffs bw EJB-QL and SQL