Developer (Eclipse) crashes with update to 4.1.4

Classic Servoy
1

I’m having a tough day. After attempting to update Servoy to v. 4.1.4 from 4.1.1 on one of my computers, I can’t get Eclipse to launch and work with my solutions with the latest version. This is on a Mac with OS 10.5.8. Here’s the sequence:

  1. Ran servoy_updater.jar from the existing application directory. All went well as it installed up to build 681.
  2. Launched Servoy Developer - it displayed the splash screen showing version 4.1.4 and then progress bar advanced to the end – then the applications crashes. Tried to relaunch several times, but the same thing occurred. I turned on the Java Console, but it doesn’t come up when developer launches. However, the launch process was recorded in console.log - I’ve attached a portion of this log to this post. When launching, an exception is thrown saying that "Widget disposed too early! Followed by several java.lang.StackOverflowError exceptions.
  3. I then did a clean install of build 681 using latest Servoy installer and a clean workspace. Eclipse/Developer launches and opens fine.
  4. Reconnected Developer 4.1.4 to database servers (all ok) and then attempted to import my projects from the earlier workspace I was using with 4.1.1. I get a stack overflow error when importing my main (rather large) solution.
  5. Tried to build the new workspace instead by checking out the solutions from my database repository - I get the same stack overflow error when checking out the same solution.

I note that a similar problem was reported that was supposedly fixed in 4.1.1 - viewtopic.php?f=11&t=11697.

Since I (stupid me) did not copy my previous (4.1.1) Servoy directory, I reinstalled a clean copy of 4.1.0 from an earlier install jar I had and was able to import my solutions into that workspace and things appear to be fine - only with 4.1.0.

Since the problem seems to occur when building the workspace for a fairly large solution, is there some switch that I can set that will enable the project to import into 4.1.4 without causing the overflow? Should I file this as a bug or am I doing something wrong?

2

Hmm - it didn’t like a file with .log extension. Here’s a second try…

console._log.txt (18.4 KB)

3

did you make a case with that stacktrace?