Hello. I tried searching the forums for this but I didnt find anything. When doing the Time Trial, after a few problems the applets stop loading. I check my java console and it says:
Exception in thread "AWT-EventQueue-1" java.lang.OutOfMemoryError: Java heap space
I'm using Firefox but it doesn't work with IE either. My Java settings say that there is no limit to the amount of memory Java applets can use. Any ideas?
{Posted by Sampi}
Java out of memory
Java out of memory
I'm having the very same problem.
After solving a certain number of problems in Time Trial it won't load another problem, and when I check with Task Manager I see that Firefox takes a lot of memory.
Also, I noticed that after I solve a problem and go to the next one the memory used by Firefox is increased. I think that the program is not releasing the last problem from the memory after the next one is called and all the memory is being used untill it can't load another problem.
If the one who wrote the code for the application will look into it he will be able to say if that's it (I don't use Java so I can't check my self).
P.S the memory is not released untill the browser is closed.
{Posted by Sas}
After solving a certain number of problems in Time Trial it won't load another problem, and when I check with Task Manager I see that Firefox takes a lot of memory.
Also, I noticed that after I solve a problem and go to the next one the memory used by Firefox is increased. I think that the program is not releasing the last problem from the memory after the next one is called and all the memory is being used untill it can't load another problem.
If the one who wrote the code for the application will look into it he will be able to say if that's it (I don't use Java so I can't check my self).
P.S the memory is not released untill the browser is closed.
{Posted by Sas}
well, when a page closes, circular pointers or no, all data should be tagged for deletion. when a page closes, there are no more references into the structures that existed.
the other thing is that a jvm doesn't necessarily free memory as soon as it can. if you manually tell it to run the gc does it still appear to leak?
adum
{Posted by admin}
the other thing is that a jvm doesn't necessarily free memory as soon as it can. if you manually tell it to run the gc does it still appear to leak?
adum
{Posted by admin}
memory
The problem is still here, and I believe I'm not the only one facing it.
When I solve problems, every problem makes firefox to eat at least 5 more Mb of memory (I believe the size is dependent on size of the problem tree).
I think this is quite important issue, did u try to make make destructors for suspicious classes?
You could try to manualy delete the applet or something like that.
I'm willing to help with this.
{Posted by kovarex}
When I solve problems, every problem makes firefox to eat at least 5 more Mb of memory (I believe the size is dependent on size of the problem tree).
I think this is quite important issue, did u try to make make destructors for suspicious classes?
You could try to manualy delete the applet or something like that.
I'm willing to help with this.
{Posted by kovarex}