cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
88
Views
0
Helpful
0
Comments
cdnadmin
Community Member
This document was generated from CDN thread

Created by: null on 25-08-2005 05:49:57 PM
I'm using Audium 3.3. I'm having trouble loading one of my apps -- I've never experienced this issue with other apps.

When I try to load the workspace, I get the error "There was an error loading the application. Do you wish to recreate the application?". If I choose No, then try to load the workspace 3 or 4 more times, it will eventually load. But why won't it load on the first try?

Subject: RE: error loading application
Replied by: null on 26-08-2005 09:34:18 PM
I don't know if this is a related symptom, but occasionally I am unable to copy/paste elements -- when this happens I see a StackOverflowError in the console.

Subject: RE: error loading application
Replied by: Michael Bochynski on 26-08-2005 10:50:35 PM
Hi jonathon,

The errors you are getting mean that Audium Builder runs out of memory and might corrupt your application.

Let me explain the details. Audium Builder by default has the allowed memory used set to 128MB (minimum) and 256MB (maximum). You can find those settings in the startBuilder script as first parameters for java (-ms128m -mx256m). Those values will tell java to allocate a minimum of 128 MB of memory and not to exceed 256 MB. In reality the temporary memory allocation can be bigger than 256MB, but this parameter tells Java to run a garbage collector when memory allocation reaches this value.

However, if the sum of memory allocated by all processes running on your machine will reach the physical memory, all the programs will start to slow and java might eventually crush. Unfortunately it might crush while saving the serialized file, thus corrupting it.

The solution is to put some memory contrains, such as minimizing the maximum allowed memory for builder to allocate. Java will, from time to time, use more memory than "allowed", but this setting will force a garbage collection to run more often, hence preventing from crushes. We would suggest setting the maximum allowed memory allocation to approximately 1/4 of your physical memory, and minimum value to 1/8. For example if your system has 512 MB of physical memory, the parameters should be set to -ms64m -mx128m. However you might want to experiment with those values. You should also see the increase of performance, since the physical memory will not be "maxed out".

Moreover setting the native stack size to 1MB also helps to avoid builder file corruption. You can modify native stack size by -ss parameter, hence in this case the additional parameter for startBuilder script would be -ss1m.

Hope this helps,
Michael

Subject: RE: error loading application
Replied by: null on 26-08-2005 11:25:26 PM
Thanks Michael. That seems to make sense. However, my PC has 1GB of memory. So, I have been using the recommended maximum memory setting of 1/4 of the physical memory (min: 128, max: 256). Maybe it is the stack size that is the culprit here. What is the default setting for the stack size?

As you suggested, I will need to try some different settings to see what works.

Jonathon

Subject: RE: error loading application
Replied by: Michael Bochynski on 29-08-2005 04:13:47 PM
Hi Jonathon,

Please modify the stack size. We have tested Audium Builder 3.3 with stack size set to 1MB, by adding a -ss1m parameter, and it worked fine.

You might want to do tests with min and max memory set to the same value. This would force Java to allocate the memory during start up and maintain it at the same level. Note if you do Save/Save & Generate during garbage collection, it might cause problems and lead to corrupted Builder files. If you have min and max memory set up to same values, GC will not do extensive collection, hence less likely to fail during Save.

Regards,
Michael
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links