Help needed for [ERROR] [lmv] Stack overflow; to increase the stack size, use the -Xss flag at startup (java -Xss1M ...)

2010-11-07 Thread Jeff Schwartz
When running in development mode I get the following error: [ERROR] [lmv] Stack overflow; to increase the stack size, use the -Xss flag at startup (java -Xss1M ...) 1) Is this error common or does it indicate something seriously wrong with my application? 2) What how do I configure to avoid

Re: Help needed for [ERROR] [lmv] Stack overflow; to increase the stack size, use the -Xss flag at startup (java -Xss1M ...)

2010-11-07 Thread Jeff Chimene
It's not an unusual condition. It is entirely possible that your compiled project code exceeds the default stack allocation. One thing I've found is that simply adding an element or two to a UI XML will cause this exception. Increase the stack size. Also, this has been discussed previously on this

Re: Help needed for [ERROR] [lmv] Stack overflow; to increase the stack size, use the -Xss flag at startup (java -Xss1M ...)

2010-11-07 Thread Jeff Chimene
On 11/07/2010 09:17 AM, Jeff Schwartz wrote: Thanks, Jeff. I modified my run configuration in Eclipse adding -Xss1M (please see the attached image). I still get the same error. Also, using Google Reader I searched the group for similar messages but I couldn't find any. BTW I am running on

Re: Help needed for [ERROR] [lmv] Stack overflow; to increase the stack size, use the -Xss flag at startup (java -Xss1M ...)

2010-11-07 Thread Jeff Schwartz
Thanks, Jeff. Xmx was and is currently set at 512m. I upped my stack memory to 50m but still throws the same error. Ideas, anyone? Jeff On Sun, Nov 7, 2010 at 12:22 PM, Jeff Chimene jchim...@gmail.com wrote: On 11/07/2010 09:17 AM, Jeff Schwartz wrote: Thanks, Jeff. I modified my run

Re: Help needed for [ERROR] [lmv] Stack overflow; to increase the stack size, use the -Xss flag at startup (java -Xss1M ...)

2010-11-07 Thread Jeff Schwartz
Resolved my bad (head slapping sound)! I fell for an old trap: I made numerous changes to my code and 1st test raised the error. Instead of checking for the new code causing the problem I believed the exception I blamed the environment. The short of it is that I refactored a class to use an