> > What does top report? > > <https://lh6.googleusercontent.com/-AFOB0QB749I/VO1aEmLWogI/AAAAAAAAAdI/aNfoNjeNTSw/s1600/top_with_pianobar_normal.png>
<https://lh5.googleusercontent.com/-P2k1r12PM68/VO1aX82URWI/AAAAAAAAAdQ/YzLGc_pfams/s1600/beagelbone_with_pianobar_stutter.png> When pianobar is running as it should: (I'm inserting a screen shot---I hope it works). and when pianobar falls into a stutter top looks like this. The big change seems to be with CPU usage rather than memory: > How much free memory do you have? > Doesn't seem to be a problem, but see the top screen shots > Have you created a swap file? > Doesn't seem to have been activated. > > Strange behaviors like this can happen when you start to run out of > memory and malloc() returns NULL (most programs don't really properly > handle this) or the kernel's OOM killer starts randomly killing processes. > > Thanks for thinking about this. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
