Bugzilla – Bug 10916
SC crashing the computer
Last modified: 2012-03-12 23:34:05 UTC
SC works for bit, but it crashes the system after a while. The crash could happen in a couple of hours or a couple of days. When the crash happen the MAC computer goes to very slow mode in responding to any input. I got the server, scanner and system log. On the system log I noticed at the end of the file there was an error with Malloc function, Malloc function is a C function that allocate memory dynamically. This leads me to think there is a memory leak some where. SC = 7.3.2 MAC 10.5.6 RN = (090119-001245)
Created attachment 4730 [details] System log
Created attachment 4731 [details] SC server log
Created attachment 4732 [details] SC scanner log
The system is running out of memory. Home much RAM does it have? How much free disk space? Looking at the process viewer - is SC swalling insane amounts of memory? Growing? Any 3rd party plugins installed?
(In reply to comment #4) > The system is running out of memory. Home much RAM does it have? How much free > disk space? Looking at the process viewer - is SC swalling insane amounts of > memory? Growing? Any 3rd party plugins installed? > Sir: The machine in question has 1.5 gigs of RAM. There are no 3rd party plug ins//haxies//etc. installed. If left unchecked the runaway process will start to eat up hard drive space. I have a 120 gig drive, with 90 gigs free. I have seen all but 10 gigs eaten when I left the machine running after an occurence of the bug.
Stephen - you say SC is eating your disk? Please check Library/Logs/SqueezeCenter: is server.log huge?
(In reply to comment #6) > Stephen - you say SC is eating your disk? Please check > Library/Logs/SqueezeCenter: is server.log huge? > The server.log file is not huge; normally I kill the machine long before it starts to devour hard drive space - and I am not sure it would in every instance but I would be willing to try if it would be helpful.
I'm only trying to understand why you're running low on disk space. The log says you were running out of memory. Is SC swallowing insane amounts of memory, leading to huge disk swapping? If this is reproducible, could you monitor the squeezecenter task (perl) in the system monitor? What's its memory usage?
Created attachment 4749 [details] System Log
Created attachment 4750 [details] Server Log
Created attachment 4751 [details] Scanner Log
Created attachment 4752 [details] MDNS Log
(In reply to comment #8) > I'm only trying to understand why you're running low on disk space. The log > says you were running out of memory. Is SC swallowing insane amounts of memory, > leading to huge disk swapping? If this is reproducible, could you monitor the > squeezecenter task (perl) in the system monitor? What's its memory usage? > Ok after approx. 1 hour after starting the server we have another machine lock-up/crash. The system log file is not large. I've noticed that if the machine becomes sluggish (ie out of memory) it will then usually eat hard drive space. This time the OS locked up completely; I did not hear the hard drive running. I have enclosed four additional log files, all dated today (2.3.09). Thanks. Stephen
The mDNSResponderPosix log specifically mentions the SC preference pane.
going one the server log most recently provided, it seems that startup is trying to use the server.memory debug option. This option tries to load a number of non-standard perl libraries in order to create a log of memory usage by module. Adding the required modules would stop that crash. I can only assume that the other 3 logs will be pointing out the fact that SC crashed, as shown in the server log.
We are now planning to make a 7.3.3 release. Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future. Thanks!
Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out. If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it. Thanks.
For some reason Bugzilla did not change the target when I did this yesterday. Or maybe it was me. In either case, I'm trying it again.
Stephen, do you still see this issue with 7.3.3?
Unassigned bugs cannot have a priority.