Dirk,
Is there something in the .Write() method which saves the image to a file that might not be multithread safe?
My app was crashing few times a day at random and I was thinking it is probably due to any of the filters it uses, however by luck i discovered it is because of the .Write() method. I needed to stop saving images to hdd for few days and noticed since then my app didn't crash even once. When i reenable saving to disk, it starts crashing again at random..
There's no exception or something thrown, directly those windows error reporting messages "this program has stopped working".. and some crash stuff in Magick.net.dll
Since it happens randomly, i don't think it is because of particular image, so i don't think this can be replicated with particular image..
All i am doing in a multithreading environment is generating a random filename string and then using .Write() to save the image
I will appreciate if you have time to look at that part of the code..
Is there something in the .Write() method which saves the image to a file that might not be multithread safe?
My app was crashing few times a day at random and I was thinking it is probably due to any of the filters it uses, however by luck i discovered it is because of the .Write() method. I needed to stop saving images to hdd for few days and noticed since then my app didn't crash even once. When i reenable saving to disk, it starts crashing again at random..
There's no exception or something thrown, directly those windows error reporting messages "this program has stopped working".. and some crash stuff in Magick.net.dll
Since it happens randomly, i don't think it is because of particular image, so i don't think this can be replicated with particular image..
All i am doing in a multithreading environment is generating a random filename string and then using .Write() to save the image
I will appreciate if you have time to look at that part of the code..