Version 7.0.1 released

Announcements about Universal Media Server
Rara
Posts: 3
Joined: Mon Apr 16, 2018 7:24 am

Re: Version 7.0.1 released

Post by Rara » Tue Apr 17, 2018 12:23 am

Looks like the application run`s out of memory.
I have 16 GB Memory and at start of the application only 4.3 GB allocated to others

DEBUG 2018-04-16 14:17:18.154 [main] Default logfile folder set to: C:\ProgramData\UMS
DEBUG 2018-04-16 14:17:18.323 [main] LogBack started with configuration file: C:\Program Files (x86)\Universal Media Server\logback.xml
DEBUG 2018-04-16 14:17:18.340 [main] Mon Apr 16 14:17:18 CEST 2018
DEBUG 2018-04-16 14:17:18.342 [main] Reading cred.path: "C:\ProgramData\UMS\UMS.cred" (default: "")
DEBUG 2018-04-16 14:17:18.750 [main] Writing PID: 6984
DEBUG 2018-04-16 14:17:18.760 [main] Reading show_splash_screen: false (default: true)
DEBUG 2018-04-16 14:17:18.761 [main]
INFO 2018-04-16 14:17:18.761 [main] Starting Universal Media Server 7.0.1
INFO 2018-04-16 14:17:18.768 [main] Based on PS3 Media Server by shagrath, copyright 2008-2014
INFO 2018-04-16 14:17:18.791 [main] http://www.universalmediaserver.com
INFO 2018-04-16 14:17:18.791 [main]
INFO 2018-04-16 14:17:18.791 [main] Build: 185b243f3 (2018-04-15)
INFO 2018-04-16 14:17:18.791 [main] Java: Java HotSpot(TM) Client VM 1.8.0_161 (32-bit) by Oracle Corporation
INFO 2018-04-16 14:17:18.793 [main] OS: Windows 10 64-bit 10.0
INFO 2018-04-16 14:17:18.797 [main] Maximum JVM Memory: 742.4 MiB
INFO 2018-04-16 14:17:18.804 [main] Language: German
INFO 2018-04-16 14:17:18.805 [main] Encoding: UTF-8
INFO 2018-04-16 14:17:18.805 [main]
INFO 2018-04-16 14:17:18.805 [main] Working directory: C:\Program Files (x86)\Universal Media Server
INFO 2018-04-16 14:17:18.815 [main] Temporary directory: C:\Users\Edmund\AppData\Local\Temp\UMS
INFO 2018-04-16 14:17:18.818 [main] Logging configuration file: C:\Program Files (x86)\Universal Media Server\logback.xml
INFO 2018-04-16 14:17:18.818 [main] Logfile: C:\ProgramData\UMS\debug.log
INFO 2018-04-16 14:17:18.818 [main]
INFO 2018-04-16 14:17:18.818 [main] Profile directory: C:\ProgramData\UMS
INFO 2018-04-16 14:17:18.820 [main] Profile directory permissions: drwx
INFO 2018-04-16 14:17:18.821 [main] Profile configuration file: C:\ProgramData\UMS\UMS.conf
INFO 2018-04-16 14:17:18.822 [main] Profile configuration file permissions: -rwx
INFO 2018-04-16 14:17:18.824 [main] Profile name: Rara-Home
INFO 2018-04-16 14:17:18.824 [main]
DEBUG 2018-04-16 14:17:18.825 [main] Reading web_conf: "C:\ProgramData\UMS\WEB.conf" (previous: null, default: "C:\ProgramData\UMS\WEB.conf")
INFO 2018-04-16 14:17:18.825 [main] Web configuration file: C:\ProgramData\UMS\WEB.conf
INFO 2018-04-16 14:17:18.827 [main] Web configuration file permissions: -rwx
INFO 2018-04-16 14:17:18.827 [main]
DEBUG 2018-04-16 14:17:18.856 [main] Using database URL: jdbc:h2:C:\ProgramData\UMS\database\medias
INFO 2018-04-16 14:17:18.856 [main] Using database located at: C:\ProgramData\UMS\database
ERROR 2018-04-16 14:17:24.699 [main] Error updating tables: Nicht genug Hauptspeicher.
Out of memory.; SQL statement:
CREATE INDEX TYPE_ISTV_SIMPLENAME on FILES (TYPE, ISTVEPISODE, MOVIEORSHOWNAMESIMPLE) [90108-196]
DEBUG 2018-04-16 14:17:24.709 [main] Database file count: 30485
DEBUG 2018-04-16 14:17:24.710 [main] Database version: 13
DEBUG 2018-04-16 14:17:24.710 [main] Starting check of database tables
ERROR 2018-04-16 14:17:24.719 [main] A serious error occurred during Universal Media Server initialization: Die Datenbank ist bereits geschlossen
The database has been closed [90098-196]

johng
Posts: 3
Joined: Mon Apr 16, 2018 4:38 am

Re: Version 7.0.1 released

Post by johng » Tue Apr 17, 2018 2:33 am

I found a fix. The problem is related to the removal of the "All Developers" option in "Settings - Privacy and Security - General" in Sierra and High Sierra. The option can be enabled in Terminal and then everything works OK. :D

User avatar
SubJunk
Lead Developer
Posts: 2655
Joined: Sun May 27, 2012 4:12 pm

Re: Version 7.0.1 released

Post by SubJunk » Tue Apr 17, 2018 9:21 am

squadjot wrote:
Mon Apr 16, 2018 12:12 pm
Just a quick fyi, when i press "download latest update" button in 7.0 i just get the "No update avail"-msg
Thanks squadjot, I just tested and it works for me, can you test again? Maybe it was a network caching thing

erick diangilis
Posts: 129
Joined: Sun May 22, 2016 8:25 am

Re: Version 7.0.1 released

Post by erick diangilis » Thu Apr 19, 2018 12:16 am

hi subjunk i've tested out this new version on ps4 media player it's working fine and i'm glad that freezing bug caused memory usage is gone.
keep up with the good work if i found any bugs i'll let you know in the future but for now is doing good. :)

Dosageko
Posts: 12
Joined: Fri May 10, 2013 7:24 am

Re: Version 7.0.1 released

Post by Dosageko » Thu Apr 19, 2018 5:14 pm

SubJunk wrote:
Mon Apr 16, 2018 6:21 pm
That must be happening for a non-English language? You can help us fix it in Crowdin
i dont think its a language thing.

in the manual it means:
Hide # Transcode # Folder
You can choose to not show this virtual folder on your device.

in the gui the checkbox means "hide transcode folder"

but in ums.conf the variable is "show_transcode_folder"

so if i set true for the "hide transcode folder" checkbox it will set true for the "show_transcode_folder" setting in ums.conf

JDN165
Posts: 4
Joined: Wed Apr 04, 2018 6:47 pm

Re: Version 7.0.1 released

Post by JDN165 » Thu Apr 19, 2018 6:17 pm

After an unsuccessful evaluation of version 7.0.0, where after several days UMS wouldn't start anymore (kept hanging in the splash screen), I reinstalled 6.8.0.
A few days ago I installed 7.0.1 (after I first completely uninstalled 6.8.0 and deleted all UMS folders). I did choose the “clean install” option.
There were no problems with the installation on my Win10 pc.
However, after I streamed FLAC audio files for some days without problem on my Sangean WFT-3 media player, UMS again won’t start anymore. No hanging in the splash screen like 7.0.0, but just… nothing. When I start UMS I see an hourglass (the turning Win10 wheel) for some seconds and then nothing happens. Just like my 7.0.0 problem, restarting the pc won't help, UMS refuses to start (until I remove everything and reinstall the program).

So, unfortunately I again had to reinstall version 6.8.0 to play my music. This version didn't give me any problem since I'm using it.

Am I really the only one with this “7.X.X won’t start anymore after some days” problem?

User avatar
Supermanfan77
Posts: 109
Joined: Thu Jun 05, 2014 4:17 pm

Re: Version 7.0.1 released

Post by Supermanfan77 » Fri Apr 20, 2018 8:21 am

JDN165 wrote:
Thu Apr 19, 2018 6:17 pm
After an unsuccessful evaluation of version 7.0.0, where after several days UMS wouldn't start anymore (kept hanging in the splash screen), I reinstalled 6.8.0.
A few days ago I installed 7.0.1 (after I first completely uninstalled 6.8.0 and deleted all UMS folders). I did choose the “clean install” option.
There were no problems with the installation on my Win10 pc.
However, after I streamed FLAC audio files for some days without problem on my Sangean WFT-3 media player, UMS again won’t start anymore. No hanging in the splash screen like 7.0.0, but just… nothing. When I start UMS I see an hourglass (the turning Win10 wheel) for some seconds and then nothing happens. Just like my 7.0.0 problem, restarting the pc won't help, UMS refuses to start (until I remove everything and reinstall the program).

So, unfortunately I again had to reinstall version 6.8.0 to play my music. This version didn't give me any problem since I'm using it.

Am I really the only one with this “7.X.X won’t start anymore after some days” problem?
That has happened to me. What fixed it for me was opening the "Task Manager" (Ctrl+Alt+Delete) and looking for, and ending the task for, an open Javascript. That's what prevented UMS opening for me and once that was closed UMS started right up.

User avatar
SubJunk
Lead Developer
Posts: 2655
Joined: Sun May 27, 2012 4:12 pm

Re: Version 7.0.1 released

Post by SubJunk » Fri Apr 20, 2018 10:10 am

JDN165 wrote:
Thu Apr 19, 2018 6:17 pm
After an unsuccessful evaluation of version 7.0.0, where after several days UMS wouldn't start anymore (kept hanging in the splash screen), I reinstalled 6.8.0.
A few days ago I installed 7.0.1 (after I first completely uninstalled 6.8.0 and deleted all UMS folders). I did choose the “clean install” option.
There were no problems with the installation on my Win10 pc.
However, after I streamed FLAC audio files for some days without problem on my Sangean WFT-3 media player, UMS again won’t start anymore. No hanging in the splash screen like 7.0.0, but just… nothing. When I start UMS I see an hourglass (the turning Win10 wheel) for some seconds and then nothing happens. Just like my 7.0.0 problem, restarting the pc won't help, UMS refuses to start (until I remove everything and reinstall the program).

So, unfortunately I again had to reinstall version 6.8.0 to play my music. This version didn't give me any problem since I'm using it.

Am I really the only one with this “7.X.X won’t start anymore after some days” problem?
It would be really useful to have logs for this since I can't fix a bug if I can't reproduce it (I can't) and I don't have logs. Instructions at viewtopic.php?f=9&t=556

JDN165
Posts: 4
Joined: Wed Apr 04, 2018 6:47 pm

Re: Version 7.0.1 released

Post by JDN165 » Fri Apr 20, 2018 7:26 pm

To create a log I must (according to the link):
  • Start UMS
  • Go to the Logs tab
  • Press the "Create TRACE logs" button which restarts UMS in the TRACE mode. If that doesn't work for some reason, either select "Trace" from the "Log Level" dropdown at the bottom or set "log_level = TRACE" in the configuration file and restart UMS manually.
  • Reproduce the bug
  • ....
This won't be easy, since in both cases I wasn't able to start UMS....

User avatar
SubJunk
Lead Developer
Posts: 2655
Joined: Sun May 27, 2012 4:12 pm

Re: Version 7.0.1 released

Post by SubJunk » Fri Apr 20, 2018 9:03 pm

You're right, those instructions don't apply to you. My mistake. But there will still be logs. Are you on Windows? If you are, the file is probably at C:\ProgramData\UMS\debug.log

Post Reply