Changeset 13542
- Timestamp:
- 08/28/11 07:46:16 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
public_html/faq.shtml
r13483 r13542 37 37 </li> 38 38 39 <li><a href="#running">Running</a> 40 <ol> 41 <li><a href="#maxpermgen-errors">Java is running out of memory an error reporting something about "java.lang.OutOfMemoryError: PermGen space". What can I do?</a></li> 42 </ol> 43 </li> 39 44 </ol> 40 45 … … 56 61 contributions in this area would be greatly appreciated, of course. 57 62 </p> 58 59 63 </div> 60 64 … … 86 90 if you distribute ABCL, but otherwise the license of ABCL is not viral. 87 91 </p> 88 89 92 </div> 90 93 … … 93 96 94 97 <p> 95 96 98 The current state of issues can be found in the <a 97 99 href="http://trac.common-lisp.net/armedbear/report/1">ABCL issue 98 tracker</a>. Unfortunately, due to spamming problems, administration 99 of bugs has been closed for anybody but common-lisp.net members.</p> 100 101 <p> 102 103 To report a bug, please mail a description of the problem, the version 104 of ABCL you are using, and if possible a set of steps to reproduce the 105 problem to the <a 100 tracker</a>. Individuals with an <a 101 href="http://en.wikipedia.org/wiki/Openid">OpenID</a> such as a Google 102 ID may enter information directly in the bug tracker after 103 authenticating by your provider. </p> 104 105 <p> 106 107 Alternatively, to report a bug, please mail a description of the 108 problem, the version of ABCL you are using, and if possible a set of 109 steps to reproduce the problem to the <a 106 110 href="http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel">armedbear-devel 107 111 mailing list</a>. We try to respond within a day at most to messages. … … 139 143 plenty of room for improvement in the area of execution speed and optimization. 140 144 The project welcomes initiatives to improve performance.</p> 141 142 145 </div> 143 146 … … 165 168 improve this measure too.</p> 166 169 167 <p>ABCL 0.26. 1fails roughly 20 out of 21702 tests in the ANSI test170 <p>ABCL 0.26.2 fails roughly 20 out of 21702 tests in the ANSI test 168 171 suite in interpreted and compiled modes, a constant number over the 169 past releases. Most failures relate to pretty printing.</p>172 past releases.</p> 170 173 171 174 <p>As a measure of 'improvement achieved', the development team refers … … 174 177 'only' ca 75 failing tests at the time of 0.15.0, and even 1400 failures 175 178 around October 2008.</p> 176 177 179 </div> 178 180 … … 188 190 <a href="http://svn.common-lisp.net/armedbear/trunk/abcl">http://svn.common-lisp.net/armedbear/trunk/abcl</a> 189 191 </p> 190 191 192 192 </div> 193 193 … … 205 205 href="http://trac.common-lisp.net/armedbear/browser/trunk/abcl/examples">examples</a></li> 206 206 </ol> 207 208 </div> 207 </div> 208 209 209 </div> 210 210 … … 223 223 the <code>abcl.build.incremental</code> property. 224 224 </p> 225 226 </div> 227 </div> 225 </div> 226 227 </div> 228 229 <div class="h2" title="Running" id="running"> 230 <h2>Running</h2> 231 232 <div class="h3" title="Out of Memory errors" id="maxpermgen-errors"> 233 <h3>Java is running out of memory an error reporting something about "java.lang.OutOfMemoryError: PermGen space". What can I do?</h3> 234 235 <p> 236 You need to increase the memory which the Java allocates for 237 permanent generation ("PermGen)" objects by using the appropiate 238 switch on command line which invokes the JVM hosting ABCL. When the 239 implementation compiles or loads Lisp code, it creates a separate 240 JVM class for each top-level form. With large workloads, this can 241 overrun the part of memory which Java reserves for storing the class 242 definition which results in the error you are seeing. 243 </p> 244 245 <p> 246 The exact manner of configuring this option which unfortunately 247 varies by implementation. For the Oracle HotSpot 64bit JVM, 248 something like <code>"-d64 -Xmx4g -XX:MaxPermSize=1g 249 -XX:+CMSClassUnloadingEnabled"</code> will not only increse the 250 PermGen space, but will ensure you always invoke the 64bit JVM, 251 increase the maximum memory space available to the JVM to 4Gib, and 252 allow the JVM to garbage collect class definitions which its deems 253 to be unused. 254 </p> 255 256 <p> 257 If you are compiling ABCL from source, a handy way to have the build 258 process incorporate such runtime flags in the JVM invocation would 259 be to copy the <code>'abcl.properties.in'</code> file to <code>'abcl.properties'</code>, and 260 then ensure that the <code>'java.options'</code> variable is set to the desired 261 options. 262 </p> 263 </div> 264 265 </div> 266 228 267 </div> 229 268
Note: See TracChangeset
for help on using the changeset viewer.