I’m working with a developer who is having a problem when using the eclipse environment with servoy developer 4.1
A couple of times per hour, servoy will become unresponsive and needs to be shut down losing any unsaved developments.
The machine running servoy is Windows XP sp 3 with 1 GB of RAM and a pentium 4 processor with 3 Ghz.
Also running on this machine might be MS office or quickbooks. I don’t think it’s the hardware, any ideas on what it might be?
Apparently there is no specific trigger that causes it to freeze. It will freeze about once or twice per hour (time related perhaps) when editing a method.
It can happen when editing any method with only one editor open. I hope it’s just a memory problem, I agree 1 GB isn’t a lot, but I believe it should be enough to run servoy developer without having to force quite twice an hour.
I have 1 instance of Eclipse open for days without interruption and…
1 or 2 instances of Servoy 4 Eclipse for hours a day without any issue.
Including much more.
And, yes I have 3GB of memory but it is on OS X which is not the best supported platform by Java/Eclipse so there definitely is something wrong with that machine/environment or whatever…
Running a laptop with simular specs here, but I can’t confirm the problems.
Hang-ups occur almost never (and even then they are often my own fault…).
What really can slow down eclipse is many global methods, because they’re all in one file.
Using ctrl-C can eclipse look like ‘hanging’, but it will always restore.
In previous ‘4’ versions there have been issues on the performance, but as far as my experience goes, they’ve been solved.
jkipling:
The machine running servoy is Windows XP sp 3 with 1 GB of RAM and a pentium 4 processor with 3 Ghz.
With these specs my first recommendation is to get him a new machine. Even though Servoy is capable on running on that I’d upgrade instead of trying to figure out which Pentium4 bug or windows driver or setting is causing the delay…
isnt it always random when that happens?
Or are you debugging and then altering code and so on?
Or do you get specific errors first in the client (that could be programming errors) and then a lock happens?
Because if you dont do nothing in eclipse i lockup doesnt happen. So there must be some trigger.
Are you sure that there isnt a dialog some where hidden that blocks all other ui?
Thanks for the reply. I haven’t had any more reports of this happening again. Nothing has changed with the machine being used, but it must have been something with the environment at the time. With all of the other processes that could have been run I don’t think the problem can be identified. If it happens again I think the solution is to use a better machine as Jan suggested.