Date: Fri, 29 Mar 2024 07:28:44 +0000 (UTC) Message-ID: <1741925525.10957.1711697324373@911f0a1bad02> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10956_1322954150.1711697324372" ------=_Part_10956_1322954150.1711697324372 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Below are some troubleshooting tips and tricks when working with= Servoy.
The output of Servoy Developer/Eclipse is written in currentWorkspaceDir= ectory/.metadata/.log. Note that on some operating systems the .XXX di= rectories/files are hidden by default.
When experiencing slow performance or out of memory errors, the maximum v= alue for the memory that Servoy Developer is allowed to use can be increase= d. See Increasing Memory Al= locations.
At the bottom of the Servoy Develo= per window is a indicator that says how much memory is used. The first numb= er 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.<= /span>
Users can click the Garbage can ic= on clicked to trigger a cleanup of the memory. This action is typicall= y not necessary, because Java does this automatically, but it may be perfor= med on command as needed.
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 re= medy is to close all editors before shutting down Servoy/Eclipse.
Linux users have been experiencing= complete freezes or crashes of Servoy Developer when using Java 6. Reverti= ng to Java 5 fixes this problem.
Due to an incorrect implementation= inside Java on OSX, it it not possible to debug when dialogs are being sho= wn in the Debug Client. Any breakpoint set will be ignored. Unfortunatly, t= here is no workaround, except using a different platform.