Sounds like there are two issues being discussed here: 1. Memory leak in your application 2. Bug in Netbeans profiler.
For the first one, I don't think anyone can help without the code, unfortunately. I have found this article to be useful in the past: https://www.toptal.com/java/hunting-memory-leaks-in-java It is a tricky thing. The profiler can definitely help - the first step would be to confirm that it is an accumulation of 'Transmitters' that's filling memory. Sometimes it's useful to deliberately restrict the java heap and force a hard memory error. For the second one, as Geertjan says, if you can take a project that we all have access to (the Anagram Game sample project built into netbeans is a good one) and let us know the exact steps that reproduce the error it would be a huge help. If it can be reproduced it can be fixed! Thanks, peter --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
