avoiding memory over-consuming

[itaipee]

Hi

An application that I made take a lot of memory. a lot.

The application include GUI and managment of small database - and yet, if open for several days without reset - I see it consumes 700 MB

I start read about

My main Class , called Seal.
Many object and many method , static and regular , have the main class as argument

i.e.
public ActionListenerToSeal2(Seal seal1, String key1,JCheckBox b1){ .. }
public static boolean verifyStatusChange(Seal seal, String key) {... }
private void updateSpcVarFromGloabl(Seal seal) { .... }

I I understand right - having 'Seal seal ' as an argument prevent this object to be deleted ?

[Addez]

I dont know but I would guess so, Why else would it be named seal?

[itaipee]

Seal is just the name of the main object - which control both GUI and database. its object that open only once and exist as long as the program is working

the question is - if temporery objects that link the this primary class - will remain in the memory ? is that the root cause of my memory problem ?

If do - what can I do instead of linking to the main object

[masijade]

No, having "Seal seal" as an argument does not prevent anything from being garbage collected. Analyse your code. Are you maybe adding things to maps or lists and then not deleting them when no longer needed?

[Tolls]

Yep.
Grab a heap dump and analyse that. There's lots of tools around for it (Eclipse has a pretty decent one I've used before). They'll point you at the most likely culprit. Which'll probably be a Collection of some sort.