Error after update

[AnthonyEd]

The file configuration is now being used:

resourceInfo: browse request after 1334917 ms
resourceInfo: heap bytes used 12529752, consumed 15193752, committed 38981632, max 253427712
resourceInfo: non-heap bytes used 42721136, committed 46792704, max 1325400063
resourceInfo: server config request after 38385828 ms
resourceInfo: heap bytes used 12627680, consumed 20584256, committed 38981632, max 253427712
resourceInfo: non-heap bytes used 43683296, committed 47054848, max 1325400063

I then tried VLC again and the same crash occurred. I'm happy to do some debugging.

[simoncn]

Please do the following:

1) Leave the resourceInfo and javaopts settings in place
2) On the System tab of the MinimServer configuration web page, set the .logLevel property to info
3) Stop VLC
4) In Package Center, stop MinimServer and restart it
5) On the System tab of the MinimServer configuration web page, set the .logLevel property to debug
6) Start VLC and do some browsing until MinimServer crashes
7) Compress the minimserver.log file in the appData directory (this step is important)
8) Attach the compressed minimserver.log file to a post here. If it is too large to attach (more than 500 KB), let me know and I will let you know how to get it to me.

Many thanks!

[simoncn]

Thanks for sending the log. It shows that VLC is opening thousands (literally) of HTTP connections to read embedded images from your files. MinimServer uses a separate thread for each HTTP connection, so there are thousands of threads active with each thread consuming a significant amount of memory. This might work on a powerful machine with gigabytes of RAM but it is overloading your DS120j beyond its capacity.

[AnthonyEd]

Thanks.

Presumably BubbleUPnP doesnt do this?

I assume there is no way of multiplexing these requests? Or is it something different?

[simoncn]

The log shows that UPnP Browse requests sent by the control point are being pipelined and multiplexed onto a small thread pool. These are not the cause of the problem.

The problem is caused by HTTP GET requests sent by the control point to download artwork images. These are not pipelined, so the control point is opening a new HTTP connection for each GET request and closing it after MinimServer has responded. The correct way to do this (if it is necessary) is for the control point to open a small pool of HTTP connections and pipeline these GET requests onto this connection pool.

This pipelining needs to be done by the control point. MinimServer cannot avoid the overhead of opening an HTTP connection for any HTTP request that isn't pipelined.

As well as this problem with HTTP connections, another issue is that VLC appears to be "scraping" the server for the entire library including all artwork images. Most UPnP control points (including BubbleUPnP) don't do this but just read those portions of the library that the user has chosen to browse.

It is the combination of all of these factors that is causing memory usage with VLC to expand unmanageably in the way that you are seeing. BubbleUPnP is an excellent control point, well designed and efficiently implemented, and will not cause the memory usage problems you are seeing with VLC.

[AnthonyEd]

I had an error with minimserver and it stopped. Tried it but error logs (minimserver-out.log) said:

Invalid maximum heap size: -Xmx250mx
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Removed the file 'minimstart.conf' and it worked. Rebooted NAS. Added the file again and the same error. The only way I could fix was by removing the file again.

The issue surfaced after trying to write genre tag data to some mp3/flac files. The tag value had previously been 'XXXX' and then it was blank and then it was 'XXXX' again.

I could not get a rescan to recognise the tag value after it had been set back to a value it previously had (prior to being blank).

[simoncn]

You need -Xmx250m, not -Xmx250mx.

[AnthonyEd]

(08-03-2026 21:59)simoncn Wrote:  You need -Xmx250m, not -Xmx250mx.

Thanks. Not sure why it was happening but the additional 'x' was being added automatically. Created a brand new conf file and that seems to work.