Servoy Developer 7 and 8 crash on MacOS

Sadly it crashed again with the jfxpanel bean removed.

then i am afraid that we only can wait if a next eclipse version will fix it (8.3) or that oracle fixes it in the jvm itself.

There is another trick to instantly crash / quit Servoy on the Mac. If you click the clear console button, it also instantly vanishes…

Great.

bevil:
If you click the clear console button, it also instantly vanishes…

I guess it worked as advertised…it cleared ;)

Hi Bevil,

bevil:
There is another trick to instantly crash / quit Servoy on the Mac. If you click the clear console button, it also instantly vanishes…

I upgraded my VM to High Sierra and installed Developer 7.4.10 on it and tried to reproduce this but I can’t.
I am wondering if there is an issue with your workspace. What you can try is to create a new workspace and import the solutions into a new workspace and work from there.
(Menubar > File > Import > General > Existing Projects into Workspace (check the checkbox ‘Copy projects into workspace’))

Hope this helps.

Thank you Robert. I have noticed another little nugget from your message though. I thought there were probably some updates, and very lazily tried to update but Servoy updater jar always reports nothing to update. My Servoy is on 7.4.1. The lack of available updates made me just guess that I was assuming there were updates when there were not, and that Servoy 7.4 was light on updates (I also haven’t been motivated enough to check the Servoy announcements forum).

I will try to actually update to 7.4.10 and see if that helps… If not, I’ll clean up my workspace (although I do already have multiple workspaces for git stuff, and I think the console crashing Servoy is common in all…

Thank you…

Bevil

I think there is an issue with the auto updates in Servoy 7.4… See attached…

[attachment=2]Screen Shot 2018-01-25 at 18.00.37.png[/attachment]
[attachment=1]Screen Shot 2018-01-25 at 18.02.07.png[/attachment]
[attachment=0]Screen Shot 2018-01-25 at 18.12.16.png[/attachment]

Agree with Bevil that clearing the Console is best(??) way to reproduce the quitting problem - also triggered it when deleting @50 lines of old/unused code.

Have created a fresh install from new 7.4.10 download with new workspace and increased memory settings in servoy.ini and that seems to have improved situation with just one crash (nothing lost) yesterday in 5+ hours coding.

Just a thought: 7.4.10 has a change in the way table events are handled. This change is also present in Servoy 8. You get infinite loops in code which has worked fine before. Servoy stops responding and may crash…

I’m having a similar problem on Mac OS Sierra 10.12.6 using Servoy 8.2.2. It was working fine earlier today. Then all of a sudden pop-ups start happening: “Unhandled event loop exception Unknown error”. Click Ok. Then another pop-up Internal Error. “An SWT error has occurred. You are recommended to exit the workbench. Subsequent errors may happen and may terminate the workbench without warning…” :(

Noticed Java automatically updated today around the time this started happening. I removed the JavaAppletPlugin.plugin folder from /Library/Internet Plug-Ins/ to see if this would fix it but it didn’t.
Also, tried using a new workspace, this didn’t fix it. Also, tried starting eclipse with -clean.
Also, tried increasing memory in servoy.ini file to 2G.

Note: the current JDK will not work with Servoy, jdk1.8.0_152.jdk. In order to get Servoy working in the first place I had to delete this version and use an earlier version.

Now looks like I’m having another Java incompatibility problem with Servoy. My log has similar entries as the ones shown here.

Anyone got some suggestions on how to fix this “Unhandled event loop exception Unknown error”?

Hi Christian thanks for the info - I haven’t seen any table specific error messages and most common crash for me is deleting code or Console - however did notice that Mem usage spikes at about the time Servoy crashes.

Problem has definitely got worse since Bevil started this thread - so I’m blaming him !!