I have had this problem with each generation of QGIS and windows 7,8, and 10
Today I solved it!!!
I deleted the .qgis2 folder in my user path
Simple as that.
When QGIS opened it created a new .qgis folder and will now happily and gracefully exit. :-)
You have a great plugin named "ChangeDataSource", doing just that very easily. The only downside is that you can only do one layer at a time.
Works on any layer type, including database layers, raster, wms, wfs, etc.
Right click on layer tree to change single layer datasource of click
on icon to change datasources globally
Windows automatically generates a minidump whenever a program throws an unhandled exception: https://msdn.microsoft.com/ru-ru/library/windows/desktop/ee416349%28v=vs.85%29.aspx
You can open these minidumps with a program like WinDbg to get an idea what caused the exception:
We tried to find the reason for the exceptions when QGIS crashed quite often. Even ...
Not really - the minidump format is very difficult to extract anything meaningful out of. In my experience (as a member of the core QGIS development team) none of the team use these dump files for bug fixing. Instead of the dump file, a step-by-step description of a reliable way to reproduce the crash is greatly preferred (including attaching any required ...
UTM (like every transverse mercator projection) can not render datasets covering the whole world. Outside of the 6 degree belt of validity, shapes get distorted heavily, but everything on the backside of the cylinder will produce artefacts or crashes:
This applies especially to Northern Europe, as the belt is getting smaller there, with zero width at the ...
in the past when I disabled my plugins, the minidump error message didn't go away
But when I just moved (or cleared) the contents of the plugin folder, that is C:\Users\Rob.qgis2\python\plugins, the minidump error stopped
then I just re-installed my plugins one by one. I have also done this to improve QGIS loading speed. Eventually too many or a particular ...
Sorry, this solution does not work for me.
Had a working version of 2.14.2 under Windows 7 32-bit, but unwisely upgraded to 2.14.6 LTR. Programme would load, but crashed on all but the simplest of projects with a similar minidump error as above. Have had the same issue in 2.16.
Tried removing .qgis2 folder with no effect.
Tried deselecting plugins to see ...
I had the same problem on QGIS 2.6 64 bit on Windows 7 Home Premium with all current updates.
Crashed on saving, every time, minidump and project file saved as 0 kb file or with small invalid file.
Uninstalled metasearch catalog client and solved problem.
There were some issues with QGIS 2.6 crashing with old projects and the print composer:
You can try the latest dev build, which has some bugs fixed, or take the bugfix release 2.6.1 which is just released.
Creating a new project from scratch should be save.
You are most likely hitting the famous issue 777
There are 2 possibilities to get around this:
Upgrade to QGIS 3
Make sure the geometry is saved to a variable and not passed as temporary to keep the python garbage collector happy
geom = QgsGeometry.fromPolyline([geomFrom.asPoint(),geomTo.asPoint()])
I have tried the same tool and it crashes in my case as well. After some Google use I found out that it crashes because the data is too complex(too many vectors). Searching for alternative solution found the Delaunay triangulation tool, which allows only one parameter per turn and it's not eactly what you are looking for. Your data is correct if you were ...
This doesn't solve the problem itself but allows you to continue your work. It could be a bug.
If you can choose which version you use, try Version 2.14 or 2.16.
You can load the WFS with the functions QGIS provides.
It seems to be a bug in version 2.18.8
It was an element within the layer! Just worked out which element it was via unclicking boxes of elements within the zone it kept breaking on until it would print compose, lots of clicking later worked out the element it didn't like. Changed the code for that element/item of the layer in the attribute table and gave it slightly different symbology and it its ...