Finding a memory leak with JProfiler

preview_player
Показать описание
This screencast explains a basic strategy for solving memory leaks with JProfiler.

Рекомендации по теме
Комментарии
Автор

Great explanation. Explained the memory leak with JProfiler accurately in just 5 mins. Thank you very much!!!

rabh_dixit
Автор

Thank you very much. This video actually helped to find a leak in the code. Great explanation.

aleksandrvasko
Автор

At around the 1:48 mark you say, "... we look for the most high-level class." What does that phrase mean? Is that the class with the largest instance count? You chose the "GeneralPath" class? Why is the "GeneralPath" class the most high-level class? How do you determine which class is the "most high-level class?" Is a class in java.awt always higher than a class in java.util? If yes, then why?

Bill-gcbt
Автор

Hi Sir, how to accomplish the same with a HPROF file? it tells me that the Allocations view is not available when viewing HPROF snapshots, thank you.

diegoramos
Автор

Hi Sir, I followed the same steps and only got the same results under "Allocations" by using "Instrumentation" mode, not with "Full Sampling", that means Full Sampling is not useful to find where are the offending objects being allocated? thanks

diegoramos
Автор

Does taking snapshot from heap and transferring thread dump take a long time for you too? It's taking me forever to do that.

ThisGuyRocksLikeCrazy
Автор

How did you solve the leak in the end though? Why doesn't leakmap automatically free unused objects?

Lionmonkeyreal