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

Crash when switching from custom renderer to standard one #7

Open
alexbruy opened this issue Dec 10, 2015 · 3 comments
Open

Crash when switching from custom renderer to standard one #7

alexbruy opened this issue Dec 10, 2015 · 3 comments

Comments

@alexbruy
Copy link

When I switch from renderer created by plugin to one of the standard renderers QGIS crashes. See also http://hub.qgis.org/issues/13973

@ccrook
Copy link
Owner

ccrook commented Dec 10, 2015

Thanks for raising the issue. I think this is related to other issues which have appeared over the last year or so (first notice on Windows 64 bit platforms) seem to relate to the python SIP bindings... the C++ parts of some python objects get lost.

In this case I suspect the fix is to include a check for a null pointer on the old symbol when changing to a new in QGIS. This won't fix the python bindings issues but it will stop QGIS crashing... I guess the null pointer dereferencing should be locatable in a debugger.

@ccrook
Copy link
Owner

ccrook commented Sep 19, 2016

I don't think this is fixable within the python plugin.
Added a warning message to the plugin widget to alert user to risk..

@ccrook ccrook closed this as completed Sep 19, 2016
@ccrook
Copy link
Owner

ccrook commented Sep 19, 2016

Just one other possibility to consider, which is to see if adding VectorArrowMarker to QgsSymbolLayerV2Registry.instance() makes any difference.

@ccrook ccrook reopened this Sep 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants