Memory issues

[anitract]

Hi All,

Been using subsonic for quite a few releases and was previously running Subsonic 3.9 (WAR version) on Ubuntu 8.04 with no issues. I just did a fresh install of Subsonic 4.0.1 (the deb package version) on a fresh install of Ubuntu 10.04 (updating my home server). I had everything running beautifully, then added some podcasts and had the search index updated. Came back and it was locked up...page would not load.

Looked like a memory issue. I tried restarting the service several times (as well as sever), while all the while bumping the memory up to 150, 256, 512, then finally 1gig. That did the trick.

Looking at top right now I see JAVA using 911MB. I don't understand why this is....any thoughts what could have caused my memory requirements to have jumped like that? Subsonic was initially working at default memory levels, so, DB corrupt maybe?

[delcypher]

Have you tried looking at /var/subsonic/subsonic.log . This may notify you of possible reasons for Subsonic crashing.

[anitract]

Nothing unusual in that log file....last several lines are a bunch of searchservice entries with the last one being:

INFO SearchService - Created search index with 383000 entries.

[anitract]

My subsonic10.index file is 126MB....not sure if this is abnormally huge, but thought I'd throw it out there.

I'm curious what other users' JAVA process is using, particularly for the deb package install.

[anitract]

This might be a clue, my stats are wrong:

1,017 artists
1,109 albums
343,639 songs
2019.76 GB (~ 31,375 hours)

Should be more like 8000 songs...............

[anitract]

Found the issue, I think. Not sure if this is a bug or not though....

Anyway, in my library, I have a directory /music/ that contains subfolders by genre, like /music/rock or /music/jazz where my music is housed. Well, in my subsonic folder settings, the very first folder I had listed was /music/ instead of /music/80s. So essentially this was causing my entire catalog to be hit twice.

I corrected the typo to say /music/80s, restarted my service, and re-run my index, now I have:

jetty-6.1.x, java 1.6.0_18, Linux (68.6 MB / 111.8 MB), which is what I was expecting. Also my index file is only 2mb instead of 120mb-ish.

I'm not sure why this issue caused my memory to be 8-9 times what is listed above. Would be curious if anyone can duplicate it...

Also, the stats shown in the sidebar are still wrong though. Is there a way to reset these?

[anitract]

Stats are magically good now. I'm running around 199MB, which although still a little high, is much much better than 900.