Below are some troubleshooting tips and tricks when working with Servoy. 

General Log File 

The output of Servoy Developer/Eclipse is written in currentWorkspaceDirectory/.metadata/.log. Note that on some operating systems the .XXX directories/files are hidden by default.

Improving Slow Performance/Out of Memory Errors

When experiencing slow performance or out of memory errors, the maximum value for the memory that Servoy Developer is allowed to use can be increased. See Increasing Memory Allocations.

Manual Cleanup of Memory

At the bottom of the Servoy Developer window is a indicator that says how much memory is used. The first number is what is actually used by the active process, and the second number is how much of the maximum value is currently allocated to Servoy Developer.

Users can click the Garbage can icon clicked to trigger a cleanup of the memory. This action is typically not necessary, because Java does this automatically, but it may be performed on command as needed.

OSX: Gray Screens on Startup

Users on OSX sometimes experience gray screens when launching Servoy Developer. This is due to issues in the Java Runtime environment on OSX, which cannot be worked around. The best remedy is to close all editors before shutting down Servoy/Eclipse.

Crashes in Linux

Linux users have been experiencing complete freezes or crashes of Servoy Developer when using Java 6. Reverting to Java 5 fixes this problem.

OSX: Debugging & Dialogs

Due to an incorrect implementation inside Java on OSX, it it not possible to debug when dialogs are being shown in the Debug Client. Any breakpoint set will be ignored. Unfortunatly, there is no workaround, except using a different platform.

OSX: Servoy Developer On Java 7

See Running Servoy Developer on Java 7 on MAC OSX

Issues with the Form Editor for Servoy Mobile in Servoy 7.4

The newly introduced Form editor in Servoy 7.4 for Servoy Mobile makes use of the internal browser component of the Eclipse environment. This internal browser component wraps the browser that the operating system ships with, so Internet Explorer on Windows, Safari on OSX. When experiencing issues with the Mobile Form Editor, the first step is to replace the default browser with the Mozilla XulRunner browser component. See Install Mozilla XulRunner as internal browser for the steps involved.

Issues with the Internal Browser

Servoy Developer uses the internal browser component of the Eclipse environment in several places, like the Developer StartPage and the HTML-based Form Editor for servoy Mobile, introduced in Servoy 7.4. when experiencing issues with in the area's of Servoy Developer that utilize the internal browser, first install the Mozilla XulRunner browser component, to replace the default browser. See Install Mozilla XulRunner as internal browser for the steps involved.