1397: One time mystery or structural bug?

[WimYogya]

It only happened once, so far, but I just want to let you know the mysterious events after a MM startup with 1397.
Tried to send this same information in the usual onscreen error report message, but for unknown reasons these (frequent!) error reports often fail to be sent...

Starting up the database four strange things happened:
1. My 89000 tracks were suddenly 178.000 tracks: all double in the tracklist. After 3 minutes this was corrected, the tracklist number ok, the duplicates gone.
2. There was a song playing, i heard it, but it was NOT the song shown in bold in the now playing list, but the next one. Nor did the progress meter move. When the song ended, no new song was started. Apparently some form of hanging.
3. An error message appeared that I don't remember litterally. Something like: 'The database query could not be performed' followed by a number of query tasks (?) that were apparently impossible.
4. A literally endless stream of error messages started popping up in cascade till my screen was full, all the same content: the header was the songtitle in bold from the 'now playing' window - the content was: 'Thread creation error. Not enough storage is available to process this command.

MM could not be closed, had to do that with the Windows task manager.

[Lowlander]

Do you have the File Monitor and Podcasts enabled? As usual a debug log send to support would be best: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

[WimYogya]

Yes, both file monitor and podcasts were active upon startup.
As said: not familiar (yet) with the debug report - will look for that later.
But one question already:
If the program crashes and can ONLY be terminated with the task manager, is then upon restarting still any debug information available to create a report?
Or is that gone when the application ends?

[nohitter151]

If the program crashes and can ONLY be terminated with the task manager, is then upon restarting still any debug information available to create a report?
Or is that gone when the application ends?

No, but any logging would have been done before the crash anyway.

[nynaevelan]

I've gotten the thread creation error also, as I stated here it is hard to reproduce because it doesn't happen all the time and I do not know what triggers it. It doesn't happen alot but enough to be annoying, and always when I am in the middle of doing alot of editing.

Nyn