hi Ethan,
I’ve noticed that when running the application in Visual Studio debugger that sometimes the MrSid’s are causing the application to crash. Below is the popup window that appears. When running outside the debugger this does not appear to happen, at least not yet.
If I set the Rasters to Invisible the application runs fine in the debugger.
I believe that this was an issue in prior MapSuite versions as it does not occur in V9. This may be memory related.
A change I made with the transition to V10 was to open each raster file (about 16 total) and leave them open for the life of the application. Prior to this the raster would be opened/closed during the DrawCore method. What overhead is there leaving 16 raster files open? Could this be causing this crash that I described here?
The application does make use of auto-tile caching. I think I’m seeing that this crash occurs the first time that it has to create a tile cache for the extent. The tile might actually get created because when the application is restarted and I go back to that location it always renders properly.
I’ll wait until you provide the other fixes from the other problems and I’ll test with new DLL’s.
Dennis
This is from the Windows Event Log.
Faulting application name: OriStarVision.vshost.exe, version: 14.0.23107.0, time stamp: 0x559b788a
Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x802f667e
Exception code: 0xc0000374
Fault offset: 0x000d9aba
Faulting process id: 0x4484
Faulting application start time: 0x01d34b667fa74f2e
Faulting application path: C:\OriStarMappingIncMapSuiteV10\OriStarVision\bin\DebugNet4.6.2\OriStarVision.vshost.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 1a1ecebe-6ed2-4aa8-bb44-8ab61a3f4201
Faulting package full name:
Faulting package-relative application ID: