search

qgis / QGIS

QGIS is a free, open source, cross platform (lin/win/mac) geographical information system (GIS)
https://qgis.org
GNU General Public License v2.0
10.66k stars 3.01k forks source link

Processing extension/plugin deactivates by itself #59234

Open fabrymar opened 1 month ago

fabrymar commented 1 month ago

What is the bug or the crash?

The core-plugin "Processing - Spatial data processing framework for QGIS" deactivates by itself seemingly at random.

This results (in my case) in a missing "Extract by location" tool (German "Nach Position selektieren") in the "Vector selection" toolbar (German "Auswahlwerkzeugleiste").

I can fix the missing tool by re-ticking the checkbox for the processing extension in the "Manage and install plugins" menu.

But I'm wondering what might cause the check mark to randomly disappear?

No updates were made prior to the occurence of the issue. A new new user profile fixed the issue for a couple of days and then it occured again with the new profile.

Steps to reproduce the issue

Unfortunately I can't give much information here: I'm starting QGIS five days in a row and everything is fine. The sixth time the tool and the check mark are missing -> I fix the check mark and close QGIS. It works again for a couple of days and then it goes missing again.

No version updates were made during this time.

Versions

QGIS-Version | 3.34.4-Prizren | QGIS-Codeversion | decd43dc -- | -- | -- | -- Qt-Version | 5.15.3 Python-Version | 3.9.18 GDAL-Version | 3.8.4 PROJ-Version | 9.3.1 EPSG-Registraturdatenbankversion | v10.098 (2023-11-24) GEOS-Version | 3.12.1-CAPI-1.18.1 SQLite-Version | 3.41.1 PDAL-Version | 2.6.0 PostgreSQL-Client-Version | 16.1 SpatiaLite-Version | 5.1.0 QWT-Version | 6.1.6 QScintilla2-Version | 2.13.4 BS-Version | Windows 10 Version 1809   |   |   |   Aktive Python-Erweiterungen irmis_json_loader | 0.8 saveecobot_loader | 0.14 db_manager | 0.1.20 grassprovider | 2.12.99 MetaSearch | 0.3.6 processing | 2.12.99 QGIS-Version 3.34.4-Prizren QGIS-Codeversion [decd43dc](https://github.com/qgis/QGIS/commit/decd43dc) Qt-Version 5.15.3 Python-Version 3.9.18 GDAL-Version 3.8.4 PROJ-Version 9.3.1 EPSG-Registraturdatenbankversion v10.098 (2023-11-24) GEOS-Version 3.12.1-CAPI-1.18.1 SQLite-Version 3.41.1 PDAL-Version 2.6.0 PostgreSQL-Client-Version 16.1 SpatiaLite-Version 5.1.0 QWT-Version 6.1.6 QScintilla2-Version 2.13.4 BS-Version Windows 10 Version 1809 Aktive Python-Erweiterungen irmis_json_loader 0.8 saveecobot_loader 0.14 db_manager 0.1.20 grassprovider 2.12.99 MetaSearch 0.3.6 processing 2.12.99 ### Supported QGIS version - [X] I'm running a supported QGIS version according to [the roadmap](https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule). ### New profile - [X] I tried with a new [QGIS profile](https://docs.qgis.org/latest/en/docs/user_manual/introduction/qgis_configuration.html#working-with-user-profiles) ### Additional context _No response_
agiudiceandrea commented 1 month ago

@fabrymar, it looks like you have installed some external third-party plugins in the QGIS user profile you are using QGIS with. Please check if the issue occurs using a new QGIS user profile without any external third-party plugin installed. If it does, please provide any error message displayed both during the QGIS start up and in the Log Messages panel.

uclaros commented 1 month ago

This has happened to me in the past. My assumption was that I had probably killed QGIS while it was actually loading the processing plugin, and it considered that the plugin caused the crash and got it disabled. Would it make sense to somehow whitelist core plugins in the plugin loader watchdog or are there valid use cases that the plugin may cause QGIS to crash and needs to be disabled?

roya0045 commented 3 weeks ago

This has happened to me in the past. My assumption was that I had probably killed QGIS while it was actually loading the processing plugin, and it considered that the plugin caused the crash and got it disabled. Would it make sense to somehow whitelist core plugins in the plugin loader watchdog or are there valid use cases that the plugin may cause QGIS to crash and needs to be disabled?

I think that disabling plugin on crash/errors is a good policy given the way QGIS loads. If loading a plugin cause a significant crash, it can prevent the app from starting as it crash the plugin initialisation.

This notably happens with the processing plugin if you have associated a directory to load models and processing script and if those items have been corrupted or just have errors (from being WIP or any other issues).