Crash to desktop on export for web tile map service

sshak
sshak Global Mapper User
in Technical Support
I am using global mapper 21.1 and I'm trying to export for web as tile map service (TMS).  When I fill out all my parameters, and select the file name, the progress bar popup appears as if it is trying to write the first file and then the software crashes to desktop.
The dataset I have loaded is a shaded rendering of elevation data (SRTM 90m) with contour lines generated within global mapper atop it. 
The data from the crash in the event log is:
Faulting application name: global_mapper.exe, version: 21.10.0.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.17134.799, time stamp: 0x7f828745
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x13c0
Faulting application start time: 0x01d710387afccd8f
Faulting application path: C:\Program Files\GlobalMapper21.1_64bit\global_mapper.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: 1e5ee058-74ec-4d1e-b37b-7e9c9761edd0
Faulting package full name: 
Faulting package-relative application ID: 


Tagged:

Answers

  • bmg_bob
    bmg_bob Global Mapper Programmer
    Hello,

    I recommend that you contact Blue Marble Support directly via email (geohelp@bluemarblegeo.com) to address this issue. Please include a detailed description of your workflow, including a screen capture of the options you used, and data that can be used to reproduce the problem. Thanks.

    Cheers,
    Bob
  • Steve D
    Steve D Global Mapper User Trusted User
    I started writing a post asking if anything was found that could be shared with folks.  I was having a similar issue this morning when I came across this post searching for solutions. 

    However, (and this is being written out for the benefit of anyone else searching for "crash while exporting tiles") I resolved my issue today by copying all of my data to one area vector layer with no other cruft.  I'm still not sure why my original data (viewsheds) caused issues today to crash GM.  I've used this feature countless times on larger datasets on older, slower PC's.

    Anyway, I hope my solution is helpful to someone else out there, though doubtless, fixing the crash would be ideal.  Who knows, maybe I got lucky today.

    I also run GM 21.1 so if the problem is confirmed fixed in a newer version, that'd be good to know as well.

    Cheers!

Categories

In this Discussion