No.498
This thread is for people experiencing a full program crash after using the next/previous buttons in the manage tags dialog. If you haven't told me you have it yet, please post here with your experience with this bug. What OS are you using? Does the crash happen every time?
If you have told me, please monitor and post to this thread as we work for a solution.
No.501
File: 1426970983867.jpg (115.21 KB, 1016x786, 508:393, 14fa97f313097998ab40d73372….jpg)
Current status: I have an idea for what might be doing this. I have added it to v151, so please let me know if you still get it next week.
Related: If you get this problem, does it happen if you open the manage tags dialog:
1) With the right click menu?
2) With F3?
No.505
>>501I've only had it happen when clicking F3, but that's how I enter the tag menu 90% of the time.
No.509
For me, it only happened when I used the right click menu. It would not crash if I entered the tag menu with F3.
No.524
File: 1427235198965.jpg (133.69 KB, 638x378, 319:189, b9440e2771a87cea41a244a3f2….jpg)
I think what is happening here is:
The menu-triggered event pauses while the tag dialog is open, only concluding once it is closed. If the tag dialog switches media in that time, the underlying media container that spawned the initial menu event (and hence the popup window) gets deleted, so when the menu event tries to clean itself up, some parent or other referenced object is already deleted and hence really doesn't want to be accessed. Some memory viotation happens and a serious error is thrown, crashing everything. ~At least on some versions of Windows.~
Hitting F3 generates a key event, which obviously doesn't generate a window like a popup menu, so it has less to clean up once it is done, and doesn't have a problem.
In tomorrow's release, I've pushed the dialog spawning code to outside the menu event. If it fixes the problem, I'll make a more generalised and professional solution in case this can happen in other places in the program.