after some searching in the forum and google I didn’t find a useful hint for my problem.
I’ve received an app crash dump (OSX Sierra) from a customer that tried to save a file with our app.
As the title already states there was a EXC_BAD_ACCESS in the BinaryStream.Write method.
I was not able to reproduce this with El Capitan nor with Windows 10.
The program creates a BinaryStream with an empty MemoryBlock.
Writes all stuff (a kind of layered, image format that can be 1 or more than 500 MB) into it and then zips it.
The crash happens while writing the data to the MemoryBlock.
I wonder if this crash could be a problem of the 32-Bit memory size limit.
But then I would expect an OutOfMemoryException.
EDIT: Verified it, a OutOfMemoryException is thrown, when no memory is available, so this should not be the issue,
at least under El Capitan. but the “UnhandledException” of my app is not getting called.
I would appreciate any hint. Maybe it’s possible to check something before?
Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ff770000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler  VM Regions Near 0xff770000: MALLOC_LARGE 00000000fb98b000-00000000ff770000 [ 61.9M] rw-/rwx SM=PRV --> Submap 00000000ffff0000-00000000ffff1000 [ 4K] r--/r-- SM=PRV process-only VM submap Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_platform.dylib 0x9f761032 _platform_memmove$VARIANT$sse42 + 162 1 com.xojo.XojoFramework 0x00f1d5c7 0xe02000 + 1160647 2 com.xojo.XojoFramework 0x00f509ab BinaryStreamWrite + 146 3 de.koelling.dmixviewer 0x000731e5 BinaryStream.Write%%o<BinaryStream>s + 79 4 de.koelling.dmixviewer 0x005cd301 DMIXIO.saveDMIX%b%o<DMIXIO>o<FolderItem>o<DMIXImage>bs + 14654 5 de.koelling.dmixviewer