Bug report #14517
QGIS 2.14 Processing filter very slow/freeze
|Affected QGIS version:||2.14.0||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||fixed/implemented|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||22490|
Using the filter function in processing is very slow, it freezes QGIS for a while for each character you enter.
QGIS 2.14, 64 bit
Windows 7, 64 bit
#3 Updated by Andreas Neumann over 4 years ago
Ok - so in the toolbox "search" field?
I just tested it in 2.14 and 2.15 nightly.
I am - like you - also on Win 7, 64bit, with QGIS 64bit.
So I wonder what is the difference between your and my installation.
Can you share what processing providers are enabled? Menu "Processing" --> "Options" -- "Providers".
Can you try de-activating all the providers that you most likely don't need and see if this helps?
Just trying to find out what triggers this slowness.
#4 Updated by Andreas Neumann over 4 years ago
Also - if you don't know what a provider does or offer - better disable it. You most likely won't need it if you don't know what it does.
As an example - I never use the Orfeo Toolbox, Taudem or Lastools - because I either don't work in the domain of Photogrammetry/Hydrologic modelling or don't own a Lastools license.
#6 Updated by Giovanni Manghi over 4 years ago
- OS version deleted (
- Priority changed from Normal to Severe/Regression
- Operating System deleted (
I confirm this issue, also on Linux and also on master.
I have the impression that this happens on projects with several layers, but I have not had time yet to double check it.
#8 Updated by Maximilian Krambach over 4 years ago
I have this issue in processing 2.12.99, which is shipped with my install on qgis (debian testing), but not in processing 2.12.2 (in qgis plugin repository).
Also, I get a (GDAL) message every time I type a letter:
ERROR 4: `1' not recognised as a supported file format.
#9 Updated by Andreas Neumann over 4 years ago
very strange - I also have 2.12.99 and the search filter for algorithms in the processing toolbox is working fine.
Did you check if there is just one processing instance and no overlap of an installation in the user profile and one in the QGIS installation directory?
How about other plugins? Do you have many of them enabled? What if you disable all other plugins?
From time to time there are plugins who really mess up QGIS and interfere with other plugins ...
#11 Updated by Andreas Neumann over 4 years ago
adding this information from Claus Sørensen
On a QGIS workshop march 9. in Silkeborg, Denmark with 30+ enthusiastic newcomers to QGIS, we encountered 3 pc's with extremely slow – tending to non-functional – search box in "Processing -> Toolbox".
OS'es ranging from Win7, Win8.1 and Win10. Win7 and Win10 unknown version but with 2.14.0 also unknown bit flavour.
My Win8.1 Pro in 64-bit with QGIS version 2.14.0 in 64 bit and no administrative rights.
By elevating security on the installation folder – in my case c:\\Program Files\\QGIS Essen\\ - to allow users "change" rights, the search box became functional again – on every pc.
#13 Updated by Victor Olaya over 4 years ago
I cannot reproduce the error, but i think it might be related to the fact that the filter now tries to find the search string also in the help (the short one) of the algorithm
Those of you experiencing this that can do a small change in the code, could you try removing these 2 lines from the Processing code and see if this fixes the issue?
Thanks in advance!
#15 Updated by Victor Olaya over 4 years ago
Thanks! So it seems that the issue is in fetching that help or scanning it, which in certain systems is a bottleneck, apparently
I will disable those lines and leave the original behaviour, searching only in alg names, not in alg help. That will temporarily fix the problem
I will leave this issue open for a while, so if anyone can provide more info, please add it here
#17 Updated by Maximilian Krambach over 4 years ago
Geoalgorithm.py :90 getCopy(self) creates an instance of an algorithm with parameters.
GdalAlgorithm.py executes getCopy() to get the name of the module. It also sets parameter to "1", which later appears as output.
So somewhere one or several algorithms are executed with a parameter of "1" when initialized. From my output it seems to be some GDAL or OGR algorithm.