#FINDING A MEMORY LEAK WITH JPROFILER HOW TO#

He's not asking about 'performance', hes asking about how to chase memory leaks via a profiler. He's not concerned about performance, hes concerned about RAM usage due to memory leaks due to programming bugs. You're advise is as useful as the lowest of the low tech support, 'Oh, thats your problem? Well, you should just probably quit everything you're doing, and re-invest from the ground up in some other product or technology.' Please tell me people like you are not actually employed as programmers or programming project leads.

Its useless advice because thats not the question being asked. Last week I was profiling my code that connected to a database and retrieved data over and over.Īnd just like low tech support, he probably knows more about the alternatives than you do. Originally, I'd bumped up the memory size on my VM to let the code run, because it was analysis code and didn't need to be super efficient until we moved it over to where the public could access it. The memory leak turned out to be in Oracle's jdbc driver. The TTCItem class was not being garbage collected, and a HUGE amount of memory (think everything sent over the wire from the database) was collecting. So, as you said, I had a bottle neck hidden away in a class library, and there was nothing I could do about it.

Then I downloaded the latest oracle ojcbc14.jar, where I'd read on some forums that they'd patched the memory leak, and the problem went away. The problem was solved, the VM was running at 6M memory, and I was happy.

Finding a memory leak with jprofiler