🚀 go-pugleaf

Matthias Vigelius <mvigelius@gmx.de> wrote:
> Thanks a lot !

> I don�t think, it depends on the ram. I�ve got 256 M, this should be enough
> even for an ide.

If your app is consuming a lot of data space, its JVM will run out of heap
and start spending a lot of time running garbage collection.  Have you tried
altering the project's VM parameters to expand the size of the app's heap?

> i�ll try to get the latest version of the sun jdk.

> the application i�ve got the most problems with, is the project i�m working
> on. i guess, it has
> something to do with a certain thread, which shows "quantum mechanical"
> behaviour, which
> means it does work, if i run the debugger, or if a print out some debugging
> information, but
> does not, if i do nothing to observe it :-))

If you're using threads, and the app isn't thread safe, it's much more likely
to deadlock while running under the debugger.

For instance, if I do something with swing that I shouldn't, it will usually
lock up in the debugger before it locks up in use.  

-- 
Joi Ellis (TeamB) 
No direct email, please.
For best results, post on news server newsgroups.borland.com!
Newsgroup Info: http://www.borland.com/newsgroups/guide.html