waking up to 10–40 error popups every morning

[ClaireCJS]

sooo many popups 😓

[ClaireCJS]

version

[Aldaviva]

Thanks for reporting this, @ClaireCJS.

I wonder if another program had locked the text file for writing, preventing this plugin from saving the song metadata to that text file.

The error reporting was improved in 3.0.0-beta.1. If you're able to get this issue to happen again, can you try with that new version and paste the error message? I had neglected to include the exception class name in the error messages in older versions like 2.2.0.

[ClaireCJS]

I’m pretty sure the only program opening it for writing is yours ;)

Verified with sysinternals handle.exe

...although not at the exact moment the error message came up which would be rather impossible especially ’cause the computer is usually locked for the night’s sleep when these accumulate.

[ClaireCJS]

Also quite frankly, once the error is thrown, the older error windows should probably go away (and just be in logfile) so we don’t have to mouse around and close 20 windows. Like if i were to go on travel for a week i’d come back to hundreds of them.

[ClaireCJS]

So.. My gut says it’s because I added elapsed-time to the file, so now the file is written every second.

So while it writes the file every second ..... sometimes the handle hasn’t closed yet from the previous write. So it fails to re-write it.

I do wonder if this could have something to do with caching, especially because I use PrimoCache. I’m going to try to disable PrimoCache for my mp3 drive....

[Aldaviva]

That's a good hypothesis, I'll see if I can improve that.

[ClaireCJS]

Yea, turning PrimoCache off didn’t help. And it’s CERTAIN SONGS that throw them. Possibly due to longer filenames or longer tags? I’m on my computer an hour, no popups, then this specific song throws 3 at a time simultaneously for a total of 20 or so for just that one song. Next song throws none. Very interesting.

[Aldaviva]

If you wish, you can feel free to send me the music file and text template that triggered this issue. If I can get the same problem to happen, it might be easier for us to figure out a solution than me sending you multiple experimental builds.