Sweethome3D uses Java3D and works well on Windows and worked well on Ubuntu 12.04.
However I and other users experienced repeated crashes on Ubuntu 14.04 and Ubuntu 16.04
(All of this on the same computer).
So although I can't get the exact code for a Linux machine (I'm on windows) this suggests you have a bug with a version we can't support.
However I did notice that SweetHome3D version 5.1 added support for Java3D 1.6 pre12 into the Mac OSX code, so perhaps there's hope of moving it forward and people on this forum being able to help
I can't seem to find an easy way to get the Mac jars to download and run, to many assitive tools in the way.
Perhaps if you talk to the SweetHome3D developer he'll help you get the Mac version to run on your machine (should be literally trivial), then forward through a bug report if something similar happens.
Beta versions of Sweet Home 3D using Java3D 1.6.0 under Windows and Linux are available here.
A user reported it didn't work under Linux / Mint 18 (but fortunately, the Jar executable which allows to switch back to Java3D 1.5.2 works for him) and another Windows 10 user didn't see any progress for his problem.
Hope there won't be more bad feedback
As expected, mohican confirmed that the beta version works better on his machine under Ubuntu Linux which is encouraging. We can do nothing for abandoned Intel OpenGL drivers that claim to work, it's a known problem, Phil suggested to show at least a message in the log. Please give us more info about the bug under Linux Mint 18. I still consider that Java3D 1.6.0 is globally more reliable than Java3D 1.5.
How can I investigate about this slowness?
I used Java VisualVM to test Sweet Home 3D under Java3D 1.5.2 and 1.6.0 in the same conditions, and it didn't reveal anything that could explain this slowness. Would it be correct to conclude the GPU load is much higher? How to tune the OpenGL context? Did any other person complain of such slowness under Linux?
I have no Linux world at all, I've tested on Windows obviously but it appears very similar.
Julien are you able to lok at this? I presume this will have to be a Jogl issue, the Java3D code must surely be nearly exactly the same.