MP 0.81 (Mac): Crashing on closing tab
Moderators: helmut, XnTriq, xnview
Re: (Mac) Crashing on closing tab
It doesn't matter what's in the folder. It can be empty, contain any kind of image file, or any other filetype. The amount of files in there doesn't matter either. I don't even need to open another tab for this, I can just close the default tab and it crashes. Basically any close-action causes a crash, no matter the surrounding circumstances.
Re: (Mac) Crashing on closing tab
Yes, as well. Anything that's closable leads to a crash.
Edit: Oh look. The browser itself actually doesn't crash, only the image preview. And apparently I can close the browser without an error. I think that's new though.
Edit: Oh look. The browser itself actually doesn't crash, only the image preview. And apparently I can close the browser without an error. I think that's new though.
Re: (Mac) Crashing on closing tab
10.11.6, yes.
Re: (Mac) Crashing on closing tab
i'm unable to reproduce this crash.
i dont' understand "It doesn't matter what's in the folder. It can be empty", if the folder is empty, how do you open the image as a tab?
i dont' understand "It doesn't matter what's in the folder. It can be empty", if the folder is empty, how do you open the image as a tab?
Pierre.
Re: (Mac) Crashing on closing tab
I'm somewhat not sure anymore, and probably have confused myself along the way. At first, it crashed on closing whatever. I think removing the original broken ini-file fixed that, and then removed the "crash on browser close" part.
By now, I somewhat suspect it's due to me trying to index about 75k images in a rather short amount of time, which leads to some weird combination of cache + ini, and makes it crash. Maybe I'll just mark the ini as readonly. As this seems to be only reproducible for me, and nobody else seems to have this, we can just close the thread as well, I can live with a workaround just fine.
By now, I somewhat suspect it's due to me trying to index about 75k images in a rather short amount of time, which leads to some weird combination of cache + ini, and makes it crash. Maybe I'll just mark the ini as readonly. As this seems to be only reproducible for me, and nobody else seems to have this, we can just close the thread as well, I can live with a workaround just fine.