Every javascript link is a no-op

[JimGilliland]

I've been running Subsonic for more than a year now. Recently I learned of the Musiccabinet add-on and thought I'd give it a try.

I installed it and let it scan my libraries. Each time, when it got up towards 100,000 entries, it crashed the server - BSOD. When the server restarted, Subsonic/Musiccabinet was back where it started with no index.

I've temporarily gotten past that by eliminating all but one of my shared libraries. This time the index completed without crashing the server. I haven't yet attempted to re-add the disabled libraries, but I will want to eventually.

The big problem at present is that I can't play any music. All of the js links on the page are showing as no-ops. I can't "Play", "Enqueue", or "Add" any song to the player - the links all say "javascript:noop()".

Does anyone know how to fix this?

[JimGilliland]

Upon further investigation, it appears that "javascript:noop" is normal. So I don't know why Musiccabinet wouldn't play my music. In any event, I've uninstalled it and gone back to "ordinary" Subsonic, and everything works again. No more BSODs, and music plays fine.

[hakko]

Sorry about that experience. I'm somehow impressed as it shouldn't be possible as a Java developer to cause BSODs (Java does the memory management for you, you have to circumvent a lot of barriers to do your own mallocs). Also, people with libraries of 500.000+ tracks have it running, so there shouldn't be a limit like that. But sorry about the waste of time!

[daneren2005]

Sorry about that experience. I'm somehow impressed as it shouldn't be possible as a Java developer to cause BSODs (Java does the memory management for you, you have to circumvent a lot of barriers to do your own mallocs). Also, people with libraries of 500.000+ tracks have it running, so there shouldn't be a limit like that. But sorry about the waste of time!

Yah, it always makes me laugh a little when people blame system crashes on a app. If the app crashes, it's the developers fault. If the whole system crashes, it is most definitely NOT a problem with the code. It is hard to make a stable system crash from within a app, and it is nigh impossible to do it on accident.

[hakko]

It's also very dependent on your choice of language. You can write some ASM instructions and crash your system if you feel like it. But modern OSes sandboxes apps as much as they can, and Java is specifically designed to help developers avoid the pitfalls of memory management, which is a fine art that most developers fail at. I don't think I could cause a BSOD on a modern Windows machine by writing a Java program even if somebody paid me for it.

maybe maybe by (mis)using sun.misc.Unsafe but I don't think so.

[Ultraviolet]

JimGilliland, I'm running well in excess of a 500,000 track library on MC without issue. In fact, MC has nearly a 20 fold decrease in memory usage vs Subsonic and that's with an increase in consecutive users on my server. I *have* experienced what you are describing with the music simply not playing before. It appears to happen more often in Chrome, but I couldn't say that for sure. My solution has been to clear the browser cache, close and reopen the browser, then everything is fine. If you simply close and reopen the browser or just clear the cache without opening and closing the browser, music won't play (my experience at least). It definitely appears to be a browser issue (instead of server), because simply opening another browser lets music play just fine. I can't remember if I had this problem with vanilla Subsonic or not though as I haven't used it in quite some time. With the feature set of MC plus the memory optimizations, I can't imagine myself going back either.