Open Joelgranados opened 9 years ago
Joel,,
I think this is related to the segfault I found in their freeimage wrapper. I'm not sure of what we can do on windows to fix it, currently we pip install from the upstream git repo as they haven't done a release since I fixed that bug. I assume the Golkhe guy hasn't recompiled from git on windows, so we're stuck with the broken version.
K
Are you referring to 144 in timestream? if you are, what suggests this is the same bug?
1) This is a bug from phenocam.anu.edu.au and that server does not have the corrupted image from 144. The corrupted image occurred when I copied images from the server and one "didn't make it" 2) The traceback that I pasted here only happens on windows. I tested with the same configuration and I did not see it in my linux box 3) I have only seen 144 on my linux machine. It probably is triggered on Windows as well but I have not tested.
Additionally, if this was a segfault, the execution would stop. For my tests the resizing continued despite the traceback. I think this traceback is happening on one of the qt threads from pipeline -g, but am not 100% sure.
Actually I was referring to https://github.com/scikit-image/scikit-image/issues/1037
But your points still stand. It's not that.
However, #144 may be the result of that bug.
Cheers, K
On Sun, Nov 30, 2014 at 11:02:56PM -0800, Joel Andres Granados wrote:
Are you referring to 144 in timestream? if you are, what suggests this is the same bug?
1) This is a bug from phenocam.anu.edu.au and that server does not have the corrupted image from 144. The corrupted image occurred when I copied images from the server and one "didn't make it" 2) The traceback that I pasted here only happens on windows. I tested with the same configuration and I did not see it in my linux box 3) I have only seen 144 on my linux machine. It probably is triggered on Windows as well but I have not tested.
Additionally, if this was a segfault, the execution would stop. For my tests the resizing continued despite the traceback. I think this traceback is happening on one of the qt threads from pipeline -g, but am not 100% sure.
Reply to this email directly or view it on GitHub: https://github.com/borevitzlab/timestreamlib/issues/145#issuecomment-65027316
This error only happens for a few images. The rest of the images are resized correctly. here is the traceback: