Page 1 of 1
Posted: 2006-10-17T11:31:06-07:00
by magick
Which version of ImageMagick are you using? ImageMagick is theoretically thread-safe. Can you post a program that is ideally less than 50 lines that illustrates the threading problem? We need to reproduce the problem before we can offer any advice.
Posted: 2006-10-17T13:11:46-07:00
by magick
If we comment out the call to new Image() and delete the program still fails suggesting a logic error somewhere else in the program. When we run the Magick++_Demos distributed with ImageMagick, they all run to completion without complaint. We're using ImageMagick 6.3.0-0.
Posted: 2006-10-17T14:58:57-07:00
by magick
This works for us. How 'bout you?
Code: Select all
#include <Magick++.h>
#include <iostream>
#include <string>
using namespace std;
using namespace Magick;
#include <wand/MagickWand.h>
int main(int argc, char** argv)
{
Image *pImg = new Image();
delete pImg;
}
Posted: 2006-10-18T09:44:00-07:00
by magick
Our standard suggestion is to open the button workspace, typically in c:\Program Files\ImageMagick-6.3.0-Q16\Magick++_Demo, and build/run it. If it runs successfully, use the workspace as a model for your own custom workspace.
Posted: 2006-10-18T15:32:38-07:00
by magick
The IMDIsplay program that comes with the ImageMagick source distribution is a MFC project and the new operator worked fine for us.