Re: as per ANOTHER suggestion... 3.2.0 and issues. again.
Posted: Sat Dec 07, 2013 10:06 am
If you see two javaw.exe processes it is wrong. UMS wasn't quit correctly so it was started second time what is bad situation because when there are two UMS processes, UMS doesn't work correctly or at all.Monica Jae wrote:also, there are two instances of Universal Media Server on my TV, and there are two instances of Java platform Binary in task manager, which is using up over 600MB of memory. Why? One question i have is, "Since java is such a memory and resource hog, why use it? like seriously? Why not C# or ajax?" Why does anyone use java at all anymore? it's like Minecraft all over again. Unles you use "this" gpu or "this" os or have more than "this" amount of memory, your system will fail. That's why it's virtually flawless on xbox 360 is because it isn't a java platform game. I digress...
i bring this up because i noticed also with older versions, that UMS will start to "act up" after a while. video starts to skip or lag or stop all together. it's doing that now. oh, and it is working, unless you haven't surmised this by now; but not without it's problems
About UMS that is programmed in JAVA. JAVA is multiplatform and Shagrath, the founder of this UMS/PMS application programmed it in language which he understood so because JAVA

About 600MB in memory. Do you think application in C++ or in .NET, C# etc. will not use so much?

Java code itself is quite small but UMS uses buffer which have to be allocated in memory. When you browse folders, all thumbs and media info is stored in memory, all your web.conf list is stored in memory, all plugin data are stored in memory so when you browse same folder again, UMS can immediately show needed data without any repeated (slow) resolving. Browsing movies with MovieInfo plugin which gathers info from web page, all is stored in memory so next time same info is displayed directly from memory instead of slow retrieval from web again. Your buffer settings allocates your memory so using 400MB buffer will allocate same amount, but for one renderer! More renderers, more memory (every renderer uses own buffer)
So 600MB used? My UMS after week of running can use between 400 to 1600MB depending on the action in progress (when transcoding is active, more memory is allocated)
There is no reason to complain on Java
