This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
My application has error "OutOfMemory" and I try to debug GC to log file, But I don't know how to find out the cause from GC log. Does any one can help to guide me analyze GC log and suggest me the way for adjust JVM options.
Out of memory exceptions are usually pretty easy to track down. What is the stack trace of your exception? What operation are you performing when the application gets the error? Reading in a file is a common cause. Filling collections with objects and never removing them is another. If you can't identify a likely problem, get a profiler like JProbe or OptimizeIt. They let you watch memory in real time so you can track down what objects are getting allocated where.