Hello,
after installing Catalina 10.15.7 on my MacBook Pro (Retina, Year 2013, Processor Intel i5, 8GB RAM, Intel graphics HD 4000), SweetHome 3D (Version 6.6.1 purchased on Apple Store) crashes while opening an existing file or when, on a new file, I add textures.
I tried, without any good result to:
- disable the 3D options in preferences and to close the 3D window;
- update/remove and re-install JRE;
- check for troubleshootings on this forum
- check for new updates.
I have attached the log generated after the crash.
Before the update I use to have High Sierra OS (v. 10.13) and SH3D was working perfectly. Any suggestion?
Thank you.
I fear that Apple broke something in the Security Update 2021-007. As you're not alone, let's hope they'll fix it quickly.
Hi Emmanuel,
Thank you for your reply.
That's a bad news... I really hope Apple will solve the issue soon.
Hi there. Yes, SH3D crashes when adding textures on my Mac Mini 2012 (HD4000 graphics) running latest 10.15.7 security update. I've been testing also Big Sur with OCLP and 11.6.1 version crashes as well in the same conditions. Let's hope Apple will fix this ASAP. BTW my Macbook Air 2013 (HD5000) and my Mac Pro with NVidia graphips work without any trouble... So, it seems to be HD4000 (and maybe other graphics) related.
Hello I've the same problem, I can no more open my old projects, the Software crashes.
MacOS 10.15.7
Process: SweetHome3D [37944]
Path: /Applications/Sweet Home 3D.app/Contents/MacOS/SweetHome3D
Identifier: com.eteks.sweethome3d.SweetHome3D
Version: 6.0 (6000)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: SweetHome3D [37944]
User ID: 501
Date/Time: 2021-11-29 20:22:10.699 +0100
OS Version: Mac OS X 10.15.7 (19H1519)
Report Version: 12
Anonymous UUID: 45C011E6-9973-CF0A-6208-805AF5994EE6
Sleep/Wake UUID: 48491676-99A5-47B3-A2DB-938B64D8A7EF
Time Awake Since Boot: 170000 seconds
Time Since Wake: 1800 seconds
System Integrity Protection: enabled
Crashed Thread: 24 Java: J3D-Renderer-1
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000000c
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0xc:
-->
__TEXT 00000001037c7000-00000001037c8000 [ 4K] r-x/rwx SM=COW /Applications/Sweet Home 3D.app/Contents/MacOS/SweetHome3D
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics kernel error: 0xfffffffb
While Apple is fixing this issue (I hope so), Don, a user with the same problem sent me the steps he got from Apple help desk to reload Catalina and make work Sweet Home 3D again:
1) Shut the computer down holding the power button for 10 seconds.
2) Restart the computer and hold down the Command and R keys as soon as the screen comes on and loading bar completes filling
3) The screen will show macOS Utilities. Click on “Reinstall macOS”
4) Follow the prompts. The computer will run for about 20min to reload macOS. It will restart and take another 20min to boot back up.
5) Sweet Home 3D should run and open any prior files
6) The OS system may say there are updates - DO NOT LOAD them. If you load them the same problem will occur.
Thanks Don for taking the time to send your feedback.
Thank you for the update, yesterday I performed a similar solution, installing macOS in a SD Card, it is a bit slower compared with the onboard SSD, but while waiting for Apple to fix the issue, it allows me to run Sweet Home 3D without interfering with the current OS installation on the main Hard Drive.
The procedure is very easy:
1) Format the SD Card (or any external USB hard drive) in MAC OS Extended (Journal) Format with GUI Partition Map Scheme;
2) Download the macOS from Apple store;
3) Run the installer, agree to the license and, VERY IMPORTANT, click "Show All Disks";
4) Select the SD Card (or the external hard drive);
5) Click Install;
6) When the computer needs to restart, press and hold the Option/Alt button until the start up options appears, then select the driver you would like to work with;
There are many websites showing the procedure step by step with links and pictures.
I hope it can help too ;)
Could you check if the Security Update 2021-008 fixed this issue?