Bug report #7819
Updated by Jürgen Fischer over 7 years ago
I'm afraid I can't replicate this one.
I have a ~20 million feature dataset which I was viewing at 1:5000. This gives up to about 40,000 features on screen. I was panning around testing QGIS speed. For my final pan, I panned just a millimetre or so and released the mouse.
QGIS then hung and started perpetually loading. You can see the process explorer report attached - RAM use was increasing, there was consistent IO, and CPU usage was 2/3rd's of one core (two core machine - 50% is one full core).
This was the only visible layer.
No idea what caused it and can't replicate it but figured I should report it.
Oracle 10g using native connection.
QGIS 1959182 on Windows 7 64bit.
I have a ~20 million feature dataset which I was viewing at 1:5000. This gives up to about 40,000 features on screen. I was panning around testing QGIS speed. For my final pan, I panned just a millimetre or so and released the mouse.
QGIS then hung and started perpetually loading. You can see the process explorer report attached - RAM use was increasing, there was consistent IO, and CPU usage was 2/3rd's of one core (two core machine - 50% is one full core).
This was the only visible layer.
No idea what caused it and can't replicate it but figured I should report it.
Oracle 10g using native connection.
QGIS 1959182 on Windows 7 64bit.