Hi Trevor,
just guessing: Is your plugin applying the
editingStarted()/editingStopped() signals? If not there are plugins
around that do it and are known to slow down QGIS. So if it is not your
plugin first thing would be to unload _all_ plugins and see if the
problem persists. If not reload the plugins only one at a time to
identify the one causing the problem.
Bernhard
Am 20.08.2014 01:42, schrieb Trevor Wiens:
I'm working on a QGIS plugin where I need to commit changes every time a
new feature is added in an SQLite database. I was using
layer.startEditing()
layer.addFeature(feature, False) OR layer.addFeature(feature, True)
layer.commitChanges()
After about 10 to 15 features the system began to slow significantly
with periods of 100% CPU usage increasing until the system became unusable.
To assess if this was my code or something in QGIS 2.4 on Debian Wheezy,
I created a simple point shapefile and added points and saved each time
(both trying just saving and stopping editing and saving) and again at
about 10 to 15 points the system failed.
My request is simple.
1. Can someone else confirm that this happens on other systems
2. If so, is there some way around this until this fixed?
Thanks
TSW
--
Trevor Wiens
Apropos Information Systems
aproposinfosystems.com <http://aproposinfosystems.com>
Calgary, Alberta
Ph. 403-973-5901
Fax 780-666-4580
__________ Information from ESET Mail Security, version of virus signature
database 10283 (20140820) __________
The message was checked by ESET Mail Security.
http://www.eset.com
_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
