Changes between Version 4 and Version 5 of Doc/compiler/problems


Ignore:
Timestamp:
Mar 7, 2007, 2:26:19 PM (19 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Charles Loomis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/compiler/problems

    v4 v5  
    1919The last line with gives the maximum amount of heap memory used and the maximum available (the value marked "heap").  If the maximum used is more than about 80% of the maximum available, then you should consider increasing the memory allocated to the java virtual machine.  See the section [Doc/compiler/running Running the Compiler] for how to specify the VM memory.
    2020
     21= Thread Management =
     22
     23== WARNING: missing modifyThread permission ==
     24
     25The java-implementation of the pan language compiler is completely multi-threaded.  Internally, it controls several thread pools to handle compilation, execution, and serialization in parallel.  At the end of a compilation, the compiler will normally destroy the thread pools that were created.  The java security model requires that a program have the "modifyThread" permission to destroy threads.  In some environments (notably eclipse), this permission may not be given to the compiler.  If this is the case, then the message "WARNING: missing modifyThread permission" is printed on the standard error.  Lacking this permission causes a "thread leak", but the effects are minor unless an extremely large number of templates are being compiled.  If this is the case, then you should either change the configuration to grant this permission to the compiler, or work in an environment that grants it by default (e.g. using ant from the command line).
     26