when I'm trying to unassociate a large number of movies, i.e. 314, it will simply freeze.

Thanks

I doubt it's a matter of quantity.

Can you confirm you're using the latest version 4.20.7?

I just did an update now. Will try again.

I got a GR3 when it froze (temporarily) now.

Perfect, that's the kind of freeze that I suspected, thank you very much for your feedback!

Here's the fixed version:

https://www.coollector.com/FREEZE/Coollector.exe

As a bonus you get a few improvements before everyone else

[NEW] "D-12" is displayed when the next episode of a series will air in 12 days
[NEW] added "Series (airing new episodes)" to the series filter
[NEW] you can mark an episode as "watched" (until now you could only give a rating)

Thanks Hector, I'll give it a try.

FYI I got error code GR12 when it froze (for a short time) a few days ago. Don't know if that helps you in any way.

Cheers,

John

If you were using the very latest version of the app, yes it means that there's still a bug out there.

The good thing with those freezes that show a code error, it's that they're easy to reproduce. Do you remember what you were doing? Can you tell me what to do to get the same freeze?

Yes, I was dissociating a large batch of movies.

And you confirm you were using the latest version 4.20.8?

I insist because I've made a first attempt and it didn't freeze on me. I need to be sure fefore I make further testings.

That is correct.

From this error message, I can tell that the "recently owned" filter was set when you've dissociated the movies. But I must be missing something because it doesn't freeze for me when I try to reproduce. Can you think of something else that I should do to be in the exact same conditions as you? Can you try again with no filter at all?

You said that you were dissociating a large batch of movies. I wonder if it's possible that it's so large that it takes several seconds to execute and the app confuses it with a freeze. Could you try with a smaller batch?

I don't have any more files to disassociate, so I'm not sure how I can try to reproduce it. As I said, it was a short freeze.

I hadn't understood this part.

I thought that when you received this kind of message, the app was frozen for good. That seems to confirm that the operation took several seconds and the app confused it with a freeze. I will look at my code and see if I can avoid this kind of confusion.

That's great, case closed