Skip to content
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

Exit Error after valid end programm #389

Closed
sawt00th opened this Issue Jan 15, 2019 · 5 comments

Comments

Projects
None yet
2 participants
@sawt00th
Copy link

sawt00th commented Jan 15, 2019

Python 3.6.5 (x32)
Windows 7
ImageMagic 7.0.8-23 Q16 (32bit) (2019-01-02)
Test Example:

` from wand.image import Image

    img1 = Image(filename=baseline_file)
    img2 = Image(filename=output_file)

    
    img1.normalize()
    img2.normalize()


    comparison, diffrence = img1.compare(img2, metric='root_mean_square')

Result: stdout:Process finished with exit code -1073741819 (0xC0000005)`

And gettng Windows crach error GUI message like:
APPCRASH Application name: python.exe application version :3.6.5150.1013

@emcconville

This comment has been minimized.

Copy link
Owner

emcconville commented Jan 16, 2019

Hey! Thanks for posting this. Looks like this was introduced with this patch. It boils down to python's ctypes not having access to CC's preprocessors results.

Luckily, wand 0.5.0 has a temporary workaround for 32bit runtimes. If you can, set the environment variable WAND_REAL_TYPE=c_double. Perhaps even in your script before loading wand modules.

import os
os.environ['WAND_REAL_TYPE'] = 'c_double'
from wand.image import Image

img1 = Image(filename=baseline_file)
img2 = Image(filename=output_file)

img1.normalize()
img2.normalize()

comparison, diffrence = img1.compare(img2, metric='root_mean_square')

@emcconville emcconville self-assigned this Jan 16, 2019

@emcconville emcconville added the bug label Jan 16, 2019

@emcconville emcconville added this to the 0.5.1 milestone Jan 16, 2019

@sawt00th

This comment has been minimized.

Copy link
Author

sawt00th commented Jan 16, 2019

I was try use your patch, but problem wasn't solved.

@emcconville

This comment has been minimized.

Copy link
Owner

emcconville commented Jan 16, 2019

I think I have this solved. If you're up for some testing -- checkout branch issue_389 @ dd3ab5d.

Not really ready to be merged into the release pipeline, but seems to have resolved the issue on win32.

@sawt00th

This comment has been minimized.

Copy link
Author

sawt00th commented Jan 17, 2019

Yes. i confirm that.
With your patch, problem was been solved.

@sawt00th sawt00th closed this Jan 17, 2019

@emcconville

This comment has been minimized.

Copy link
Owner

emcconville commented Jan 17, 2019

Great! I'll finish up regression testing shortly, and include the revision in the 0.5.1 release. Thanks for testing the branch, it really does help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.