Todd Kneib#27252
We are moving our application to support x64 OSs due to our direct driver to the printers, so the app has to run 64bit on 64bit OSs.
I've run up against a wall though, when I call Aurigma.GraphicsMill.Codecs.FormatManager.CreateFormatReader
It throws "Arithmetic operation resulted in an overflow."
It also happens when I call new Aurigma.GraphicsMill.Bitmap(filename)
This happens on Window 8, 64bit. If I set the target to x86, it works, which makes sense as System.IntPtr.ToInt32() should fail on 64bit.
What is weird though is that these calls work just fine with platform target x64 on Windows 7, 64bit. I have several clean virtual machines, and they consistently fail on Win8 64bit, but not Win7 64bit.
We are using the latest 5 series, 5.5.6.
I've attached my test app.
I've run up against a wall though, when I call Aurigma.GraphicsMill.Codecs.FormatManager.CreateFormatReader
It throws "Arithmetic operation resulted in an overflow."
at System.IntPtr.ToInt32()
at Aurigma.GraphicsMill.Codecs.BmpReader.OnCheckForSupport(Stream stream)
at Aurigma.GraphicsMill.Codecs.FormatReader._CheckForSupport(Stream stream)
at Aurigma.GraphicsMill.Codecs.FormatReader.CheckForSupport(Stream stream)
at Aurigma.GraphicsMill.Codecs.FormatManager.CreateFormatReader(String fileName)
at AGx64Test.Program.worker.GetPixelDimensionsOfImage(String imageFilename)
at AGx64Test.Program.DoWork(String filename)It also happens when I call new Aurigma.GraphicsMill.Bitmap(filename)
at System.IntPtr.ToInt32()
at Aurigma.GraphicsMill.Codecs.BmpReader.OnCheckForSupport(Stream stream)
at Aurigma.GraphicsMill.Codecs.FormatReader._CheckForSupport(Stream stream)
at Aurigma.GraphicsMill.Codecs.FormatReader.CheckForSupport(Stream stream)
at Aurigma.GraphicsMill.Codecs.FormatManager.CreateFormatReader(String fileName)
at Aurigma.GraphicsMill.Bitmap.Load(String fileName)
at Aurigma.GraphicsMill.Bitmap._Load(String fileName)
at Aurigma.GraphicsMill.Bitmap..ctor(String fileName)
at AGx64Test.Program.worker.OpenFile(String filename)
at AGx64Test.Program.DoWork(String filename)This happens on Window 8, 64bit. If I set the target to x86, it works, which makes sense as System.IntPtr.ToInt32() should fail on 64bit.
What is weird though is that these calls work just fine with platform target x64 on Windows 7, 64bit. I have several clean virtual machines, and they consistently fail on Win8 64bit, but not Win7 64bit.
We are using the latest 5 series, 5.5.6.
I've attached my test app.