Java heap space

[mike963]

I have about 125,000 music files on a Synology DS415Play

When I run MinimServer I get a Java heap space error

after 3000 lines of warnings - any ideas ?

java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOfRange(Arrays.java:2694)
at java.lang.String.<init>(String.java:203)
at java.lang.StringBuilder.toString(StringBuilder.java:405)
at org.jminim.core.LogImpl.printlnSync(LogImpl.java:680)
at org.jminim.core.LogImpl.println(LogImpl.java:127)
at com.minimserver.FileReader.readFileData(FileReader.java:112)
at com.minimserver.Server.readMetadata(Server.java:5423)
at com.minimserver.Server.scanFiles(Server.java:3907)
at com.minimserver.Server.scanFiles(Server.java:4031)
at com.minimserver.Server.scanFiles(Server.java:4031)
at com.minimserver.Server.scanFiles(Server.java:4031)
at com.minimserver.Server.scanFiles(Server.java:4031)
at com.minimserver.Server.readFiles(Server.java:3453)
at com.minimserver.Server.doStart(Server.java:1974)
at com.minimserver.Server.start(Server.java:469)
at org.jminim.core.ContextImpl.startComponent(ContextImpl.java:160)
at org.jminim.core.ContextImpl.start(ContextImpl.java:85)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:1233)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:827)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav​a:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jminim.launch.Launcher.doLaunch(Launcher.java:502)
at org.jminim.launch.Launcher.launch(Launcher.java:140)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:30)
MinimServer error: now stopped, use 'relaunch' or 'exit'

[simoncn]

(08-12-2014 00:28)mike963 Wrote:  I have about 125,000 music files on a Synology DS415Play

When I run MinimServer I get a Java heap space error

after 3000 lines of warnings - any ideas ?

java.lang.OutOfMemoryError: Java heap space

MinimServer error: now stopped, use 'relaunch' or 'exit'

Please do the following:

1) Use MinimWatch to set the resourceInfo property to 5000
2) From MinimWatch, select 'Show log' and leave the log window open
3) From the DS Package Center, stop and restart MinimServer
4) The log window will contain periodic resource updates mixed in with the warnings. When you get the failure, copy and paste the most recent resource update into a post here.

[mike963]

Many thanks for the quick response
I did those changes and it started and after an hour it stopped so I restarted I now I see this in the log window when set to debug

MinimWatch 0.8.2 update 21, Copyright © 2012-2014 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot™ 64-Bit Server VM (build 25.25-b02, mixed mode)
Platform default charset is windows-1252
Active subnet is 192.168.1.0
Startup complete
starting MinimServer[DiskStation]
stopping MinimServer[DiskStation]
MinimServer[DiskStation] is stopped
starting MinimServer
09:14:30.889 AWT-EventQueue-0: User changed log level: info
09:14:30.892 Thread-44: saveProperty: compName=null propName=logLevel propValue=info
10:12:25.284 Thread-32: AllContextStatusChanged: notifyChange time=1418033545284
10:12:25.284 Thread-5: AllContextStatusChangedAction starting
10:12:25.284 Thread-5: AllContextStatus=consoleContext,Running,runtimeContext,Running,context0,Stopping​,watchContext,Running,monitorContext,Running,ohnetContext,Running,httpContext,Ru​nning
10:12:25.284 Thread-5: DeviceMonitor notifyContext: name=context0, status=Stopping
10:12:25.284 Thread-5: ServerControl: contextStopping event for context0
stopping MinimServer[DiskStation]
10:12:25.288 AWT-EventQueue-0: TrayView: displaying tray icon message: stopping MinimServer[DiskStation]
10:12:25.289 AWT-EventQueue-0: TrayView: displaying tray icon tooltip: stopping MinimServer[DiskStation]
10:12:25.290 Thread-5: AllContextStatusChangedAction ended
10:12:26.265 Thread-19: AllComponentStatusChanged: notifyChange time=1418033546265
10:12:26.265 Thread-5: AllComponentStatusChangedAction starting
10:12:26.266 Thread-5: AllComponentStatus=console,org.jminim.lib.ConsoleService,consoleContext,Running,​runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,minimserver,com.min​imserver.Server,context0,Stopping,watch,com.minimserver.WatchService,watchContex​t,Running,monitor,org.jminim.lib.MonitorService,monitorContext,Running,ohnet,org​.jminim.lib.OhNetService,ohnetContext,Running,http,org.jminim.lib.HTTPService,ht​tpContext,Running
10:12:26.266 Thread-5: DeviceMonitor notifyComponent: name=minimserver, type=com.minimserver.Server, context=context0, status=Stopping
10:12:26.266 Thread-5: ServerControl: componentStopping event for minimserver
10:12:26.266 Thread-5: AllComponentStatusChangedAction ended
10:12:26.748 Thread-29: AllComponentStatusChanged: notifyChange time=1418033546748
10:12:26.748 Thread-5: AllComponentStatusChangedAction starting
10:12:26.748 Thread-5: AllComponentStatus=console,org.jminim.lib.ConsoleService,consoleContext,Stopped,​runtime,org.jminim.lib.RuntimeService,runtimeContext,Stopped,minimserver,com.min​imserver.Server,context0,Stopped,watch,com.minimserver.WatchService,watchContext​,Stopped,monitor,org.jminim.lib.MonitorService,monitorContext,Stopping,ohnet,org​.jminim.lib.OhNetService,ohnetContext,Running,http,org.jminim.lib.HTTPService,ht​tpContext,Running
10:12:26.748 Thread-5: DeviceMonitor notifyComponent: name=console, type=org.jminim.lib.ConsoleService, context=consoleContext, status=Stopped
10:12:26.748 Thread-5: DeviceMonitor notifyComponent: name=runtime, type=org.jminim.lib.RuntimeService, context=runtimeContext, status=Stopped
10:12:26.748 Thread-5: DeviceMonitor notifyComponent: name=minimserver, type=com.minimserver.Server, context=context0, status=Stopped
10:12:26.749 Thread-5: ServerControl: componentStopped event for minimserver
10:12:26.749 Thread-5: DeviceMonitor notifyComponent: name=watch, type=com.minimserver.WatchService, context=watchContext, status=Stopped
10:12:26.749 Thread-5: DeviceMonitor notifyComponent: name=monitor, type=org.jminim.lib.MonitorService, context=monitorContext, status=Stopping
10:12:26.749 Thread-5: AllComponentStatusChangedAction ended
10:12:26.772 Thread-14: ListDeviceType:jminim.org:Monitor1: device removed for udn 71032347-1730-41d7-8239-caaeecbe46a6: org.openhome.net.controlpoint.CpDevice@1bdac45d
10:12:26.772 Thread-14: ObserverService: device removed for udn 71032347-1730-41d7-8239-caaeecbe46a6: org.openhome.net.controlpoint.CpDevice@1bdac45d
10:12:26.772 Thread-5: DeviceRemovedAction starting
10:12:26.773 Thread-5: TrayControl: removed remote device
10:12:26.773 Thread-5: ServerControl: dispose
10:12:26.773 Thread-14: ListServiceType:jminim.org:Monitor1: device removed for udn 71032347-1730-41d7-8239-caaeecbe46a6: org.openhome.net.controlpoint.CpDevice@2b4fa7f8
10:12:26.773 Thread-14: ObserverService: device removed for udn 71032347-1730-41d7-8239-caaeecbe46a6: org.openhome.net.controlpoint.CpDevice@2b4fa7f8
10:12:26.773 Thread-5: ServerControl: listenerRemoved event
10:12:26.773 Thread-5: TrayView: dispose
10:12:26.774 Thread-5: ServerControl: setLogUpdates action, logUpdates=false
10:12:26.774 Thread-5: TrayView: removing tray icon
10:12:26.775 Thread-5: disposed PopupMenu peer after 0 retries
10:12:33.777 Thread-5: TrayView: removed tray icon
10:12:33.779 Thread-5: showing default tray icon
10:12:33.779 Thread-5: TrayView: adding tray icon
10:12:33.788 Thread-5: TrayView: added tray icon
10:12:33.788 Thread-5: stopping DeviceMonitor
10:12:33.788 Thread-5: DeviceMonitor.stop: disposing logProxy org.jminim.ohnet.CpProxyJminimOrgLog1@75c567a7
10:12:33.788 Thread-5: DeviceMonitor.stop: disposing monitorProxy org.jminim.ohnet.CpProxyJminimOrgMonitor1@51b0ff02
10:12:33.789 Thread-5: calling removeCpDevice
10:12:33.789 Thread-5: ObserverService: removing device
10:12:33.789 Thread-5: ObserverService: removed device with udn 71032347-1730-41d7-8239-caaeecbe46a6: org.openhome.net.controlpoint.CpDevice@78490d8b
10:12:33.789 Thread-5: ObserverService: calling removeRef for device org.openhome.net.controlpoint.CpDevice@78490d8b
10:12:33.789 Thread-14: ObserverService: ignoring removed device with unknown udn 71032347-1730-41d7-8239-caaeecbe46a6
10:12:33.789 Thread-14: ListServiceType:jminim.org:Log1: device removed for udn 71032347-1730-41d7-8239-caaeecbe46a6: org.openhome.net.controlpoint.CpDevice@59b9ce08
10:12:33.789 Thread-5: DeviceRemovedAction ended
10:12:33.789 Thread-14: ObserverService: device removed for udn 71032347-1730-41d7-8239-caaeecbe46a6: org.openhome.net.controlpoint.CpDevice@59b9ce08
10:12:33.789 Thread-14: ObserverService: ignoring removed device with unknown udn 71032347-1730-41d7-8239-caaeecbe46a6

[mike963]

stopped and restarted again - it is now scanning files again so will let you know when it finishes

[mike963]

attached is log file - it stopped at the end - hope this helps
had to zip log file

Thanks

Mike

[simoncn]

(08-12-2014 12:39)mike963 Wrote:  attached is log file - it stopped at the end - hope this helps
had to zip log file

Thanks

Mike

Thanks for doing this.

It looks like you have sent the MinimWatch log from "Options > Show log (watch)" instead of the MinimServer log from "Show log". To analyse this problem, I need to see the MinimServer log.

Please do the following:

1) From the minim icon, select "Options > Show log (watch)"
2) In the log window that appears, set the logging level to Info
3) Close this log window
4) From the minim icon, select "Show log"
5) In the log window that appears, set the logging level to Info
6) Leave this log window open
7) From the minim icon, select "Properties"
8) In the Advanced tab of the Properties window, set the resourceInfo property to 5000 and click OK
9) From the DS Package Center, stop and restart MinimServer
10) The log window that you left open in step 6 should display periodic resource updates mixed in with the warnings
11) When you get the failure, click 'Save as' in this log window to save a log file
12) Zip the saved log file and attach it to a post here

Please make sure the logging level is set to Info, not Debug. The debug log contains a lot of additional information that isn't relevant to this problem. It is easier for me to analyse the problem from an Info log.

[mike963]

Oops - sorry - hope this one helps
zipped again

Thanks again

Mike

[simoncn]

(08-12-2014 14:29)mike963 Wrote:  Oops - sorry - hope this one helps
zipped again

Thanks again

Mike

Yes, it does. It shows that the excessive memory consumption is caused by your .m3u files. Are these files very large? For example, what is in the file 2014-03-.m3u?

[mike963]

yes - they are large - just been using them to provide a better way of getting playlists on the Diskstation
they are auto generated and can't get large - that is is 1.7MB - it has 16,000 lines

So - that is good to know - is there a way to stop MinimServer was searching a specific directory as I cannot move that one as it used with the Diskstation

If not I will just get rid of the large ones - do you have any advice of what size constraint I should use ?

Mike

[DavidHB]

(08-12-2014 15:01)mike963 Wrote:  ... is there a way to stop MinimServer was searching a specific directory as I cannot move that one as it used with the Diskstation ?

Subject to correction by Simon, no there isn't; you can only specify folders (up to 8) that are scanned by MinimServer. You use MinimWatch to edit and add folder entries; the web interface can only be used to edit the first entry. Depending on where your problem folder is located, you might be able to specify the folders to be scanned in such a way that this folder is excluded.

Actually, having a '-[folder name]' option (presumably still within the 8 folder limit) would be a rather useful feature to have.

David