Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception: wrapped C/C++ object of type QgsProcessingToolboxTreeView has been deleted #53455

Closed
2 tasks
rduivenvoorde opened this issue Jun 13, 2023 · 3 comments · Fixed by #53461
Closed
2 tasks
Assignees
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@rduivenvoorde
Copy link
Contributor

What is the bug or the crash?

Screenshot from 2023-06-13 12-02-00

Steps to reproduce the issue

I cannot easily reproduce this... but in a new profile (not using processing there during session), I disabled some plugins (one of them processing), and then stopped QGIS to restart it... and then the above message popped up...

Apparently the disabling of the plugin cleaned up some stuff...?

Versions

QGIS version 3.31.0-Master QGIS code revision 678cee7
Qt version 5.15.8
Python version 3.11.2
GDAL/OGR version 3.6.2
PROJ version 9.1.1
EPSG Registry database version v10.076 (2022-08-31)
GEOS version 3.11.1-CAPI-1.17.1
SQLite version 3.40.1
PostgreSQL client version unknown
SpatiaLite version 5.0.1
QWT version 6.1.4
QScintilla2 version 2.13.3
OS version Debian GNU/Linux 12 (bookworm)

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

Additional context

No response

@rduivenvoorde rduivenvoorde added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Jun 13, 2023
@nicogodet
Copy link
Member

  1. Load a vector layer and raster layer
  2. Disable then re-enable processing plugin
  3. Open processing toolbox
  4. Click on one layer then the other in layer tree
  5. See warning

@rduivenvoorde
Copy link
Contributor Author

Yep, thanks! That is reproducible with me too.

@nicogodet
Copy link
Member

Some iface signals are connected during processing plugin initGui but never disconnected (or I missed them)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants