Re: REAL SSCCE of my graphical interface with memory leaks
Sal wrote:
On 31 Ott, 13:10, "Andrew Thompson" <u32984@uwe> wrote:
[...]
I ran 'your'* code for 8 hours on Win XP Pro using
Java 1.6.0_02**. Besides that, I also ran jconsole
(part of the 1.6 SDK, not sure of earlier versions).
GREAT!!
* You code was horrible.
Ehm... now i think that you are right.
*Please run it and confirm the same behaviour you
reported as a 'memory leak'.*
Yes I ran it for two hour and the memory grows up to 15.824 KB (Task
Manager Windows)
OTOH, if your app. actually hits OutOfMemoryErrors,
we need to look more closely at what it is doing, and
(if my addled memory serves me well) what is happening
with any Image's and ImageIcon's..
Yes I've to look in another place the problem of my memory error
(probably a memory leak ;), but i'm not a specialist i written this
program day by day not looking to the correct code but looking to make
it runs.
Now i have a program of 1300 lines of graphical interface and many
more to control it and i don't know where i have to look!
I need a tool that help me to find the problem, can you advice me a
freeware one?
....
Maybe it is time for some refactoring, with the objective of making the
program cleaner and easier to decompose, as well as ensuring all GUI
work is done in the event handling thread.
It is entirely possible that the refactoring will itself remove the
problem. If it does not, you will have a better base for SSCCE
construction. The SSCCE approach can be a good way of tracking down
problems, even if you never post them to a newsgroup. The idea is to
progressively simplify the program, removing everything that is not
essential to reproducing the bug.
In your case, the test should be whether you get an OutOfMemoryError if
you run the program with -Xmx set to a reasonable value. Any time you
remove something, and the bug goes away, you have a new clue about what
is going wrong.
Patricia