Error after update

[AnthonyEd]

Just done the update so I am on the following versions:

MinimServer 2.2 update 271
MinimStreamer 2.1.4

I got this error:

"Exception while processing action request: java.lang.OutOfMemoryError: Java heap space"

[simoncn]

This error message is not a problem with the update. It means you need to increase the heap space allocated by Java to a value that is large enough to satisfy the memory requirements of your library. What platform (Windows, Mac, Linux, QNAP, Synology, etc.) are you using to run MinimServer?

[AnthonyEd]

I am running on Synology.

This could be completely coincidental, but this seemed to happen only after I downloaded VLC onto my phone and used it with Minimserver.

I have rebooted my NAS and not attempted to use VLC and it now appears to be stable.

for info:

DSM 7.3.2-86009 Update 1

NAS is DS120j

[simoncn]

I don't think it is coincidental. It sounds like VLC is making requests to MinimServer that require a significant amount of RAM to process. These requests could be internal to VLC (for example, download and index the complete library) or possibly because of some explicit browsing or searching action on your part.

Your NAS has 512 MB of RAM. By default, Java reserves 25% of this RAM for heap data for MinimServer to use. If you are not running much else on the NAS, you could increase the maximum heap size to 200 MB or 250 MB. For details of how to do this, see this post.

[AnthonyEd]

Thanks. Done all of this. Is there a parameter I can check to see if it is using the new size? (I used 250MB)

edit: just reinstalled VLC on my phone. The same error appears. Maybe I just need to stick with BubbleUPnP?

[simoncn]

I have tried VLC on my phone and there is no problem with excessive memory usage, so I would like to investigate further to find out why you are having this problem.

What exactly are you doing in VLC? I am selecting MinimServer from the Local Network list in VLC and doing a bit of browsing.

Please set the serverOptions property to resourceInfo=1000 (or add this setting if you already have something in this property). This causes MinimServer to write information about memory usage to the MinimServer log. This information should be similar to the following:

resourceInfo: resource request after 189341 ms
resourceInfo: heap bytes used 7527024, consumed 7619112, committed 28311552, max 268435454
resourceInfo: non-heap bytes used 36602800, committed 39829504, max 1325400063

The important numbers are heap bytes used and heap bytes max. In my case the heap bytes used figure is only 7 MB. If you have done the configuration correctly and relaunched MinimServer after doing it, your heap bytes max figure should be about 250 MB (similar to mine). I am finding it hard to understand how your heap bytes used figure could be as high as 250 MB.

[AnthonyEd]

Setting resourceInfo to 1000
resourceInfo: server config request after 64724953 ms
resourceInfo: server config request after 120 ms
resourceInfo: heap bytes used 13099928, consumed 60291440, committed 127729664, max 127729664
resourceInfo: non-heap bytes used 43325168, committed 45203456, max 1325400063
resourceInfo: heap bytes used 12947488, consumed 60128632, committed 121323520, max 127729664
resourceInfo: non-heap bytes used 43325632, committed 45203456, max 1325400063

The file is as follows:

root@PhilSynNas:/volume1/MinimServer/etc# cat minimstart.conf

javaopts = -Xmx250m

[simoncn]

Thanks for this. It shows that the -Xmx250m setting is not in effect.

Did you stop MinimServer from the Package Center and restart it? This is required for the javaopts setting to take effect.

Also, the heap bytes used value is only about 13 MB. Does this grow much larger (approximately 128 MB) before you get the OutOfMemory error?

[AnthonyEd]

Yes I stopped and started. In fact I did again just now before testing again with VLC. I am only browsing with VLC.

Results as follows:
resourceInfo: browse request after 61686 ms
resourceInfo: heap bytes used 11680736, consumed 45212992, committed 99250176, max 127729664
resourceInfo: non-heap bytes used 39448896, committed 41418752, max 1325400063
resourceInfo: browse request after 62305 ms
resourceInfo: heap bytes used 14220352, consumed 58951752, committed 96436224, max 127729664
resourceInfo: non-heap bytes used 39922152, committed 42008576, max 1325400063
MinimServer: exception while processing action request: java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
at java.base/java.util.Arrays.copyOf(Arrays.java:3536)
at java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.jav​a:227)
at java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:593)
at java.base/java.lang.StringBuilder.append(StringBuilder.java:173)
at com.minimserver.Server.append(Server.java:13137)
at com.minimserver.Server.access$27400(Server.java:190)
at com.minimserver.Server$TrackItem.getDIDL(Server.java:27262)
at com.minimserver.Server$Container.getContentsDIDL(Server.java:27751)
at com.minimserver.Server$ContentDirectoryProvider.doBrowse(Server.java:34884)
at com.minimserver.Server$ContentDirectoryProvider.browse(Server.java:34818)
at org.openhome.net.device.providers.DvProviderUpnpOrgContentDirectory1$DoBrowse.ac​tionInvoked(DvProviderUpnpOrgContentDirectory1.java:978)

[simoncn]

Thanks for this. There are a few issues here:

1) The javaopts setting did not work. I suspect this is because of a file permissions issue with your minimstart.conf file that prevents the file from being read by MinimServer. If you created the file while logged into a terminal window as the root user, you need to use chmod and/or chown to make the file readable by all users. Alternaitvely, you can login to DSM as the adminstrator user and upload the file using File Station, which will automatically apply the correct permissions.

2) The resourceInfo output prior to the crash shows that only 14220352 heap bytes are in use. The figures for committed and consumed are 58951752 and 96436224, which suggests that a lot of memory is being allocated and freed as a result of VLC browsing activity.

3) The code location where the crash occurs is not doing a large memory allocation. It is appending what should be a small amount of data to what should be a fairly small string. This (together with 2 above) suggests that VLC is doing something different from other control points when it browses the library.

Would you be willing to create a debug log so that I can see what VLC is doing when you browse your library? If so, I will post instructions for doing this and sending me the log file.