#532 out of memory

closed-invalid
nobody
5
2006-09-19
2006-09-19
Anonymous
No

1 error occured! Please submit a bug report containing
the information below and an account of the actions
that caused the bug (if known) to
http://sourceforge.net/projects/drjava. You may wish to
save all your work and restart DrJava. Thanks for your
help in making DrJava better!

Discussion

  • Dan Smith

    Dan Smith - 2006-09-19

    Logged In: YES
    user_id=1060117

    Thanks for taking the time to submit a bug report, but there's
    not any information here that can be acted on.

    If you get this (or another) error again, please do a couple of
    things:

    1) Give us a summary of what you were doing when the error
    occurred, and any pertinent details about your system

    2) Click on "more information" (or something similar; alternately,
    a "DrJava Errors" button will appear on the toolbar), which will
    display a stack trace of the error and other debugging
    information. Copy and paste that text into the bug report.

     
  • Dan Smith

    Dan Smith - 2006-09-19
    • status: open --> closed-invalid
     
  • Mathias Ricken

    Mathias Ricken - 2006-09-19

    Logged In: YES
    user_id=1075744

    If DrJava itself is running out of memory, you can change
    "JVM Args for Main JVM" setting under
    Preferences/Miscellaneous to allow DrJava to use more memory
    than Java usually allocates for a program.

    For the "JVM Args for Main JVM" setting, enter something like

    -Xmx1G -Xms1G

    You need to restart DrJava after you change this setting. In
    this example, I have given DrJava 1 gigabyte (1G) of memory.
    You can also provide different amounts, like 512 megabytes
    (512M):

    -Xmx512M -Xms512M

    If you like, you can also specify these sizes at the command
    line. When you run the DrJava jar file (the name drjava.jar
    may vary), you can do something like this:

    java -jar drjava.jar -Xmx512M -Xms512M

    If your programs in the Interactions Pane run out of memory,
    you can do a similar thing and put the same kind of
    parameters, e.g. "-Xmx512M -Xms512M" in the "JVM Args for
    Interactions JVM" setting in Preferences/Miscellaneous.
    After changing them, you need to reset the Interactions Pane.

     
  • Robert Cartwright

    Logged In: YES
    user_id=430590

    For almost any conceivable project, 256M is enough heap
    memory for DrJava. When I am editing the DrJava code base
    (over 500 files), 256M normally suffices. The proper choice
    of heap size depends on the amount of main memory on your
    machine. I do not recommend setting maximium heap size (the
    -Xmx<size> argument) above about half of your main memory
    size. Most modern machines have at least 512MB of main
    memory so 256MB is a good choice. The -Xms<size> argument
    specifies the initial heap size. I usually don't bother
    setting this value because I presume that the default value
    is reasonable. Java will expand the heap as needed up to
    maximum heap size based on the demands of DrJava. On the
    other hand, the default maximum heap size is rather small
    (less than 100MB), so I generally provide a -Xmx<size>
    argument when running DrJava. BTW you can include this
    argument on the command line if you are starting DrJava from
    the command line.

    DrJava maintains a document cache of 20 documents to help
    reduce maxiumum heap requirements, but all modified document
    s must be kept in memory so they are not counted as part of
    the 20 documents that are "swapped" into main memory. If
    you do a global replace that modifies every document in a
    project, then you could conceivably need a huge heap.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks