Lacie raid manager memory leak - M1 mini
Fyi, I have been running on a M1 mini (8G, 256G) with a Lacie 5big since January 13th. I noticed (iStat) that the raid manager process lcss has a memory leak. At one time more than +1G memory size. Eight days ago it crashed with SOCD report detected: (AP watchdog expired), unrelated to the memory leak, I think? I noticed that the lcss memory size was 64mb, today 217mb. Maybe it is related to lcss being an intel application? I contacted Lacie support and was dismissed with, reinstall and call us back! Looks like I will have schedule a reboot every two weeks. Comments?
Comments
-
I haven't heard of this specific problem, but I would say that 1 GB memory usage for the RAID manager sounds anomalously high. If this is a memory leak, what you should see is that the memory usage of this one application grows steadily without limit - is this what you are seeing? If so, then eventually this could cause things like slowdowns and even kernel panics.
What I would do is to make sure all software (macOS, RAID manager) are up to date, and then document this memory usage e.g. with screenshots that clearly show it increasing steadily over time to large values. Then send this to LaCie to give them a chance to respond, and if this doesn't happen, are you able to return the 5big device?
-
Thanks Ben, Memory usage of this process grows continuously as of now 224mb and will ultimately become the highest memory usage and will continue without bounds. The macOS, Monterey and the the Lacie driver and firmware are at the latest update. I really don't use the Lacie UI so it is all based on the lcss process. As for the the 5Big it has been running 24/7 since 2018 initially on a 2012 mini then a 2014 mini now the M1 (knocking on wood). Not sure of the SOCD panic, lots of discussion on MacRumors and support.apple. My plan for now is to keep a daily log of the memory usage of the lcss process and see if it leads to the panic.
-
This certainly sounds like a memory leak in this process. It's unfortunate that this instability is a new problem, after working well for so long. It's a good idea to keep a log so that you can clearly demonstrate the problem to LaCie. You could also try a weekly scheduled reboot to try to keep things running smoothly.
