Apart from being generally crunchy to use, BS has crashed (not just the program, but the entire machine) two different M4 Mac minis (24GB RAM, Tahoe) today. The task both times was a simple set of stickers for the cutter. It wasn’t the job that caused the crash - it executed many times on both machines - it was the clock time that the program had been running, and (presumably) a memory leak. Both times a window popped up to say I was out of system memory.
Has anyone had a similar experience? I’ll open a ticket but, if it happened to me on two different machines, I imagine it’s happening broadly.
I experienced this on the latest version yesterday, when slicing a full bed of small geometries. When I rolled back to the previous version, I was able to slice without a crash. The system didn’t crash, only the program, but still very frustrating of course.
Sounds like you don’t have enough RAM or disk space to start with. Remember that you need enough free space on the system disk for about 2-4x your RAM (swap space for virtual memory).
Yes, there may be a problem with Bambu Studio, but the fragile part is your system that crashes on a minor memory leak.
Did you even read my post? I was writing about Bambu Suite. Do you really know how memory virtualization works? If a program follows the rules, the OS will swap to disk, not crash the machine. I have plenty of RAM and tons of disk. The machines went down with a system panic - reporting out of system memory. What makes you think the “leak” was minor? Thanks for providing bland generic “advice” after not reading even the subject line. The noise level around here is already too high.
Yes, I read your post - that’s why I know you don’t grasp how VM and your OS actually work. MacOS Is super fragile if the system disk is filled, so you need to keep space available for your swapfile to grow.
And on a normal, stable machine, it wouldn’t crash because of a minor leak like you’re seeing in Bambu Studio. With more RAM, the leak uses some RAM, and won’t need to touch the swapfile. Without enough RAM, the extra memory has to grow the swapfile, which is where you run into problems - because you don’t have enough space left on the system disk to grow the swapfile, hence the OS error message saying you were out of system memory (it isn’t out of RAM, you’re out of swap space). With more disk space, the swapfile would grow and the leak wouldn’t bother anything… until you ran out of disk space.
Now go re-read what I wrote, and try to understand it. And next time try asking questions of system and application developers who know far more than you… instead of attacking out of gross ignorance.
Are you really trying very hard to defend a memory leaking (and often crashing) app on reasonably good hardwares…?
I’m using a mac with 64GB ram with 2TB drive, usually the system is totally unoccupied and it still happens to me. It’s so annoying that I basically stopped using laser recently.
Please just don’t bring your job to every discussion that you happen to be in when you’re being challenged for… I dunno, obvious reasons like “don’t mind I’m just taking another 128GB of hard drive space since your 64GB RAM is obviously not enough for my memory leak that I absolutely have to leak”?
I had a lot of crashes while slicing, I can’t remember how I exaclty solved it but in a lame way it was about general gpu settings on nvidia panel that caused the issue.
perfeclty working intel i5 6500 3.20 ghz and gtx 1650 - 16gb ram 3000 mhz
fwiw, this isn’t true the way it was a decade ago. Early Mac OS X lost its mind and crashed out if it filled the boot volume. Most recent versions tell the user what the problem is and give an opportunity to fix the problem; sometimes an app is terminated too. So you still need the spare space for VM, but it’s not as fatal as it once was. (I know because I’ve bounced off that rev limiter too many times over the years…)
An earlier poster mentioned:
That seems definitive to me, and is inline with my experience of Mac OS.
No, I said nothing about defending a resource leak.The crash described is a common problem when the system disk is full and the swapfile cannot grow. It is not an application crash, despite being triggered by a memory leak - it is a problem with the system because there is not enough RAM for the processes being run, and not enough room on the system disk for the swapfile to grow to meet the needs.
Please learn to read and stop accusing people of saying things they did not say. Also, if a technical explanation sounds more complicated than you understand – go look it up instead of attacking the expert who is simply trying to explain things to you.
Yes, I’m simplifying a lot because the target audience has already demonstrated that they don’t fully understand how VM and the OS work. It would take several pages of text to describe the current OS behavior (which is an attempt to work around the fragility), and still boil down to: need more RAM, and more disk space.
Right now I’m debugging a Blizzard/Activision process that’s eating/leaking 45 GB of memory - and yet my system is still quite stable and not giving a single error message, because I know how the OS works.
There are lots of weird things with macOS, there’s also a unlikely but still possible case: when you have 0bytes left on an APFS formatted device… then you’re totally cooked.
Although they did some things to prevent it from happening, you can still see it happening from time to time online and it’s a fun experience for the other viewers, not so much fun for the owners though.
However going back to our topic. No the memory leak and crash frequency on this software is outright not tolerable. I’m fine if it crashes like once a couple weeks, but, crashing or becoming super slow after one or two slices… wtf
My Windows PC keeps freezing and has to be rebooted. I’ve come to the conclusion that it only happens when BS is open. I checked the crash logs and it’s TCPIP critical error. AI says that BS network DLLs are known to be bad.
It’s really a hassle to have to reboot several times a day. At least SSD makes it faster.
