I have exactly the same crash, with the same stack trace. I saw that the crash is inside the fglrx driver, so I removed the fglrx package and used the default ATI driver (RADEON). SweetHome3D now runs for me.
I don't know if this is a bug in Java or a bug in fglrx. I suspect the latter, but the Java maintainers will need to check it and move it over to fglrx if appropriate.
I have three almost identical log files saved, which I can attach if desired. If anyone wants me to run additional tests I can do that. However, the problem is instantly reproducible, every time, when I use SweetHome3D with fglrx.
I have exactly the same crash, with the same stack trace. I saw that the crash is inside the fglrx driver, so I removed the fglrx package and used the default ATI driver (RADEON). SweetHome3D now runs for me.
I don't know if this is a bug in Java or a bug in fglrx. I suspect the latter, but the Java maintainers will need to check it and move it over to fglrx if appropriate.
My stack trace has slightly different offsets:
hs_err_ pid20171. log:C [+0x416] __kernel_ vsyscall+ 0x2 pid20171. log:C [fglrx_ dri.so+ 0x167e8a3] pid20171. log:C [libpthread. so.0+0x5cc9]
hs_err_
hs_err_
I have three almost identical log files saved, which I can attach if desired. If anyone wants me to run additional tests I can do that. However, the problem is instantly reproducible, every time, when I use SweetHome3D with fglrx.