Page 1 of 1

Crash after DB Maintenance [#16556]

Posted: Sun Apr 26, 2020 12:39 am
by dtsig
id:47CDE118

Re: 2243: Crash after DB Maintenance

Posted: Sun Apr 26, 2020 7:14 pm
by dypsis
I get that too.
A crash log was sent.

Re: 2243: Crash after DB Maintenance

Posted: Sun Apr 26, 2020 8:08 pm
by Peke
Hi,
I am not being able to replicate.

Can you please try to replicate on clean portable MM5 install with MM5.DB that crashes?

Re: 2243: Crash after DB Maintenance

Posted: Sun Apr 26, 2020 8:47 pm
by dypsis
A clean portable installation of MM5.

These are the database management settings I have used.
Image

Here is the error.
Image

Error Details:
Image

Application Error:
Image

The log has been sent. 👍

Re: 2243: Crash after DB Maintenance

Posted: Sun Apr 26, 2020 9:39 pm
by dtsig
yep ... same error

Re: 2243: Crash after DB Maintenance

Posted: Sun Apr 26, 2020 9:53 pm
by Peke
HI,
Ok, I created bug report, can you send DL link of your compressed MM5.db to Ludek?

Added as https://www.ventismedia.com/mantis/view.php?id=16556

Re: Crash after DB Maintenance [#16556]

Posted: Sun Apr 26, 2020 10:31 pm
by dypsis
One other thing that I noticed is that there were two instances of MediaMonkeyEngine.exe running.
And when I clicked restart, I received another error that it couldn't connect to a media server because MediaMonkeyEngine.exe was already running. Only one instance shut down at restart.

Is that normal?

Re: Crash after DB Maintenance [#16556]

Posted: Sun Apr 26, 2020 10:40 pm
by dypsis
Database sent to Ludek. 😉

Re: Crash after DB Maintenance [#16556]

Posted: Mon Apr 27, 2020 4:21 am
by Peke
Hi,
Thanks, Ludek will look at it.
dypsis wrote: Sun Apr 26, 2020 10:31 pm Is that normal?
Yes it is, we added additional MM server Port checks to see if there is another instance of MM5 that is running on same port (eg. not closed or...) in order to determine if there is some issues with starting server and WiFi sync availability.

Re: Crash after DB Maintenance [#16556]

Posted: Mon Apr 27, 2020 2:43 pm
by dypsis
Thanks, Peke.

Ludek replied and said that he was able to reproduce the crash with my database.

Re: Crash after DB Maintenance [#16556]

Posted: Mon Apr 27, 2020 4:46 pm
by dtsig
let me know if you need another db

Re: Crash after DB Maintenance [#16556]

Posted: Mon Apr 27, 2020 4:52 pm
by Ludek
It is fixed in 2244+ , thanks.

BTW: Any reason why you are using "Rebuild database" option? Was your DB somehow corrupted or what was the reason?

Re: Crash after DB Maintenance [#16556]

Posted: Mon Apr 27, 2020 10:16 pm
by dtsig
For me i thought it was the "complete" option. will go without it

Re: Crash after DB Maintenance [#16556]

Posted: Tue Apr 28, 2020 1:19 am
by dypsis
Ludek wrote: Mon Apr 27, 2020 4:52 pm It is fixed in 2244+ , thanks.

BTW: Any reason why you are using "Rebuild database" option? Was your DB somehow corrupted or what was the reason?
I've been using it as part of the process of upgrading my MM4 database to MM5.
It was suggested to me in one of the threads.

If it's not needed, then let me know.
But at least we found a bug, and you fixed it. 😉

Re: Crash after DB Maintenance [#16556]

Posted: Tue Apr 28, 2020 5:28 am
by Ludek
dypsis wrote: Tue Apr 28, 2020 1:19 am If it's not needed, then let me know.
But at least we found a bug, and you fixed it. 😉
Sure, that's good that we found the bug!! ;-)
Otherwise "Rebuild database" should be needed only when you really need to completely rebuild your DB (e.g. because of a corruption, inconsistent data etc.).
It is not recommended to use it on a regular basic.
"Optimize database" can be used regularly from time to time for a houskeeping / improving performance.