-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashes due to Qt5Core.dll with D&D addition #116
Comments
Hi, Thank you very much for reporting me the problem. I tried to replicate this event and everything seems to work fine. It is possible that one of the 2 png files is corrupted in some way. Unfortunately, in certain cases, ImageMagick is not able to manage properly corrupted images even if other programs are perfeclty able to show these images. You can check the integrity of your images using the identify program: |
Umm.
I'm not sure of the detailed conditions. Sometimes when it needs to be repeated as in the following gif, and sometimes it happens on the first addition. Here's a record of the crush and the sample pair I used. |
Thank you very much for attaching the samples. I tried to replicate the event both on windows and linux and everything seems to work fine. Anyway I'll test the code more thoroughly in order to find and fix the problem! |
I was able to get application logs from the event viewer so I attach it here. I hope this helps you! My windows locale is not English so I had no choice but output as evtx format. |
Another log (
|
Thank you very much for the logs, it's not clear what generates the crash, anyway I'm investigating the causes of it |
Hi, I found a bug related to file input so I report here.
Let's say "x.png" on folder "A" exists on the list box, and if another "x.png" on folder "B" is opened, Coverseen crushes.
I'm using version 0.9.9.8.
Thank you.
(edited)
I tried with another (png) image pair, and crush did not occur.
So this problem might be related to specific png pair, but not to their name.
Does Converseen have kinds of debugging log output?
If so, I'll look into it more.
The text was updated successfully, but these errors were encountered: