Hello ~~
I've installed Subsonic server version 5.2.1 on a Banana Pro (http://www.lemaker.org/) running Ubuntu (http://www.lemaker.org/resources/9-257/lubuntu_for_bananapro.html). The Banana Pro has a SATA port. I've connected it to a 1TB HDD and am happily streaming music to my Sonos speakers, my Mom's Sonos speakers, my phone, browser, etc, and generally having a great time.
However, I'm experiencing a behavior that I've been unable to find any mention of on the web with regards to Subsonic or Banana Pro. Every few hours, Java will crash. Here is the error message in /var/subsonic/subsonic_sh.log.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (os_linux_zero.cpp:285), pid=2728, tid=2526712928
# fatal error: caught unhandled signal 11
#
# JRE version: OpenJDK Runtime Environment (7.0_79-b14) (build 1.7.0_79-b14)
# Java VM: OpenJDK Zero VM (24.79-b02 mixed mode linux-arm )
# Derivative: IcedTea 2.5.5
# Distribution: Ubuntu 14.04 LTS, package 7u79-2.5.5-0ubuntu0.14.04.2
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid2728.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
#
I don't know whether this is normal, but subsonic_sh.log also has thousands of lines of this. Every few seconds a new value gets written.
[...]
[GC 32557K->19501K(46556K), 0.0068020 secs]
[GC 32556K->19500K(46556K), 0.0067100 secs]
[GC 32556K->19501K(46556K), 0.0066310 secs]
[GC 32557K->19501K(46556K), 0.0066650 secs]
[GC 32557K->19500K(46556K), 0.0066210 secs]
[GC 32556K->19501K(46556K), 0.0067280 secs]
[GC 32557K->19500K(46556K), 0.0067360 secs]
[GC 32556K->19500K(46556K), 0.0066020 secs]
[...]
The "46556K" stays the same, but the first two values slowly creep up over time. I do not know what they mean.
When I restart subsonic it works fine, then after a couple hours the same thing happens. There doesn't seem to be any specific action that causes it. It's happened repeatedly both when the server was streaming music and when it was not. It's never happened on the same song either, or if it has, that seems to have been by chance.
I'm also going to post this on the Lemaker Boards and will update this post with a link to that post. My post in Lemaker will link here as well.
Thank you!
Edit: Here is the link to my post on the Lemaker forum. http://forum.lemaker.org/forum.php?mod= ... 544&extra=