If you install qgis-rel-dev with the OsGeo4W-Installer you can start this QGIS-version with the qgis-rel-devXXX. Even with our paid QGIS-Support we could not find the reasons for the QGIS-crashes and were told that the minidumps are not necessarily helpful.Ī better way for us was to use the QGIS-rel-dev version which writes debug-outputs and listen to these debug-outputs with a program like DebugView ( ): We tried to find the reason for the exceptions when QGIS crashed quite often. You can open these minidumps with a program like WinDbg to get an idea what caused the exception:
Windows automatically generates a minidump whenever a program throws an unhandled exception: What actually causes QGIS to crash? Could it be a hardware issue possibly? The user mentioned above, after a of week of no crash mini dump's, is again reporting that the issue is back. So I decided to uninstall 2.16, and install 2.18īut before I did this I looked for information on crash minidump and yes, the main accepted advice, which works, is to Delete C:\users\name.qgis2 before re-installingīut what is a crash minidump, what’s happening? Then myself, using QGIS 2.16, I was testing out an answer from Merging attribute and geometric features in QGIS? it gave me a crash minidump each time I tried dissolve vectors. The background leading up to this is that I have a user that has a crash minidump every time that they close QGIS (2.14.9), even though many others are using the same version, on exactly the same machines, of the same age and make without issue.
What is happening, is there a simple answer? they should be perfectly safe.There are lots of posts to do with QGIS crashing they tend to deal with specific instances and conditions.īut this has led me to want to know what is a crash minidump? The primary executable is named black ops 2 - gsc. The most common release is 16.2.15.0, with over 98 of all installations currently using this version.
Black Ops 2 - GSC Studio is a software program developed by iMCS Productions. These launchers were used since the V1 package and i just scanned them as well just in case something changed over the years but they show the same results. I suggest you to check for latest updates available for GSC. that doesn't mean the scanners didn't do their job, because if there was a real virus most would detect it no matter how big the package was. load gsc in gametypedm use this gsc and set your name as 'TheIronDragonz21' to get host and menu settings ( also you need to be the first one to connect to the server ) only you and anyone who use that name can use the menu. since these launchers are converted scripts this is probably the reason for the false positives.Īnd in case you were wondering why it looked 100% clean when i scanned the whole package, the scanners probably don't analyze every file as well when scanning large packages. I just decompiled the gsc file to get exception for host players. i have personal experience knowing a file was completely safe and clean but some scanners would still think there was a virus. Virus Scanners are notorious for sometimes detecting viruses when there are none.
If youre trying to inject GSC into the client while connecting to a server that is not yours, we will not help you.
the launchers are basically just batch files that i converted to executables. We have an official thread here on how to write and load scripts on dedicated servers, since dedicated servers are the only parts of our mod that can load custom scripts. User Mini Dump File: Only registers, stack and portions of memory are available Symbol search path is: srv Executable search path is: Windows 10 Version 10586 MP (8 procs) Free x86 compatible Product: WinNt, suite: SingleUserTS Built by: 6.0 (th2release.
i made the launchers a long time ago and i forgot which program i used to create them (maybe AutoIt). Here is a virus scan of just the launchers:Īs you can see most do not detect anything but 1 out of 5 do.