Bugs and Features

We welcome (regular) users of the GeoDMS to help us improve the software. Bug reports and feature requests can be reported here. Contact us if you are interested.

reporting issues

Before reporting an issue we ask you to check if the same or a similar issue is not already reported. New bugs and feature requests can be added by activating the New Issue button. A page appears in which the characteristics of the issue need to be specified. The characteristics presented with a * are obligatory.

Since GeoDMS 20.19.3, a crash of the GeoDMS itself, meaning a structured exception such as an access violation and not a configuration error, writes a minidump before it goes down. It lands in the CrashDumps folder of your LocalDataDir and is named GeoDms_<process id>_<date>_<time>.dmp. The fatal error dialog names the file that was written, and when you started GeoDMS with a log file the log names it too. Attach the file to the issue. It carries the stacks of every thread at the moment of the crash, which is usually the difference between a report that can be diagnosed and one that cannot. A crash on a background calculation thread is captured as well, which before produced nothing at all.

A dump is a few hundred kilobytes to some tens of megabytes: it holds those stacks and the memory they point at, not the whole process, so it can contain file names, item names and fragments of the data that was being processed, but not your whole data set. Before 20.19.3 a crash of the GUI left nothing at all, not even a message: the window simply disappeared.

getting remote support

If your organisation has a support contract, we can help you with configuration issues. We can assist you from our office by phone and a remote connection with e.g. Teams.