Dear all,
I've just changed the allocation memory on ImageJ (from 640 to1400MB). Now I want to edit a macro on the program, install and run it but when I run it, the macro quits... I don't know why... Just before having changed the allocation of the memory, I did exactly the same thing and the macro was running... Does anybody have an idea about this problem? Thanks a lot, france |
Please read the FAQ:
http://imagejdocu.tudor.lu/imagej-documenation-wiki/faq/how-do-i-increase-the-memory-in-imagej On Friday 15 September 2006 10:06, Girault France wrote: > Dear all, > > > > I've just changed the allocation memory on ImageJ (from 640 to1400MB). > Now I want to edit a macro on the program, install and run it but when I > run it, the macro quits... I don't know why... Just before having > changed the allocation of the memory, I did exactly the same thing and > the macro was running... > > Does anybody have an idea about this problem? > > > > Thanks a lot, > > > > france |
Hi,
The FAQ doesn't answer the original question (unless you consider the cryptic sentence "Strangely enough, allocating more memory to ImageJ reduces the amount of memory available for loading images!" an answer...). It sounds to me like it might be related to other problems mentioned previously on the list: https://list.nih.gov/cgi-bin/wa?A2=ind0608&L=IMAGEJ&P=R10300&I=-3 France, try decreasing the memory allocation incrementally until the problem goes away. Even if that works, though, I really have no idea what causes problems like yours. -Curtis On 9/15/06, Gabriel Landini <[hidden email]> wrote: > Please read the FAQ: > > http://imagejdocu.tudor.lu/imagej-documenation-wiki/faq/how-do-i-increase-the-memory-in-imagej > > > On Friday 15 September 2006 10:06, Girault France wrote: > > Dear all, > > > > > > > > I've just changed the allocation memory on ImageJ (from 640 to1400MB). > > Now I want to edit a macro on the program, install and run it but when I > > run it, the macro quits... I don't know why... Just before having > > changed the allocation of the memory, I did exactly the same thing and > > the macro was running... > > > > Does anybody have an idea about this problem? > > > > > > > > Thanks a lot, > > > > > > > > france > |
In reply to this post by Girault France
On Friday 15 September 2006 15:52, Curtis Rueden wrote:
> The FAQ doesn't answer the original question (unless you consider the > cryptic sentence "Strangely enough, allocating more memory to ImageJ > reduces the amount of memory available for loading images!" an > answer...). Hi Curtis, Maybe that bit is out of date, but it came from Wayne -- who should know what he is talking about :-) : https://list.nih.gov/cgi-bin/wa?A2=ind0110&L=IMAGEJ&P=R469&I=-3 I think that the first sentence of the FAQ points to a possible solution. (Isn't this also what you are suggesting?): > France, try decreasing the memory allocation incrementally until the > problem goes away. Even if that works, though, I really have no idea > what causes problems like yours. The original post did not specify what platform, OS, Java or IJ version, or more importantly RAM available. So pointing to the FAQ seemed to me the simplest way to help. If you have suggestions for that (or any other) FAQ, you can also help improving them. Please fell free to modify and add to it (the FAQs can be modified by anybody who wishes to do so (there is an approval mechanism but only to prevent vandalism to the site, as happened recently). Registration is free. :-) Cheers, G. |
In reply to this post by Girault France
Thanks a lot for these replies... It seems to be due to my processor which has 1Giga RAM memory. I decrease the allocation for the memory and I can run the macro again.... Cheers, france On Friday 15 September 2006 15:52, Curtis Rueden wrote: > The FAQ doesn't answer the original question (unless you consider the > cryptic sentence "Strangely enough, allocating more memory to ImageJ > reduces the amount of memory available for loading images!" an > answer...). Hi Curtis, Maybe that bit is out of date, but it came from Wayne -- who should know what he is talking about :-) : https://list.nih.gov/cgi-bin/wa?A2=ind0110&L=IMAGEJ&P=R469&I=-3 I think that the first sentence of the FAQ points to a possible solution. (Isn't this also what you are suggesting?): > France, try decreasing the memory allocation incrementally until the > problem goes away. Even if that works, though, I really have no idea > what causes problems like yours. The original post did not specify what platform, OS, Java or IJ version, or more importantly RAM available. So pointing to the FAQ seemed to me the simplest way to help. If you have suggestions for that (or any other) FAQ, you can also help improving them. Please fell free to modify and add to it (the FAQs can be modified by anybody who wishes to do so (there is an approval mechanism but only to prevent vandalism to the site, as happened recently). Registration is free. :-) Cheers, G. France Girault Geological Institute CAB E-62 ETH Zürich Universitätstrasse 6 8092 Zürich [hidden email] Private phone : ++4178/726.99.20 Office phone : ++4144/632 84 16 |
In reply to this post by Gabriel Landini
There seems to be some system specific factors that determine the max
memory value. I found that on my system (WinXP SP2, 2.5 GB RAM, virtual memory 768M-3G, imagej 1.37q), I can only set the -Xmx value up to 1468m. Anything more than that will cause the error "could not create the Java virtual machine" by Java Virtual Machine Launcher. Here is my start script "C:\Program Files\Java\jre1.5.0_06\bin\javaw.exe" -mx1468m -cp ij.jar;jimi.jar;C:\windows\System32\QTJava.zip ij.ImageJ Trial and error is how I get to that value. By the way, running the script on the commandline did not yield anymore information about unrecognized option. Am I missing anything here? -- Pang (Wai Pang Chan, [hidden email], PAB A087, 206-685-1519) The Biology Imaging Facility (http://staff.washington.edu/wpchan/if/) On Fri, 15 Sep 2006, Gabriel Landini wrote: > On Friday 15 September 2006 15:52, Curtis Rueden wrote: >> The FAQ doesn't answer the original question (unless you consider the >> cryptic sentence "Strangely enough, allocating more memory to ImageJ >> reduces the amount of memory available for loading images!" an >> answer...). > > Hi Curtis, > > Maybe that bit is out of date, but it came from Wayne -- who should know what > he is talking about :-) : > > https://list.nih.gov/cgi-bin/wa?A2=ind0110&L=IMAGEJ&P=R469&I=-3 > > I think that the first sentence of the FAQ points to a possible solution. > (Isn't this also what you are suggesting?): > >> France, try decreasing the memory allocation incrementally until the >> problem goes away. Even if that works, though, I really have no idea >> what causes problems like yours. > > The original post did not specify what platform, OS, Java or IJ version, or > more importantly RAM available. So pointing to the FAQ seemed to me the > simplest way to help. > > If you have suggestions for that (or any other) FAQ, you can also help > improving them. > Please fell free to modify and add to it (the FAQs can be modified by anybody > who wishes to do so (there is an approval mechanism but only to prevent > vandalism to the site, as happened recently). > Registration is free. :-) |
Free forum by Nabble | Edit this page |