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.

Sign up for GitHub

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

Jump to bottom

Crashing #22

Closed
seancarmody opened this issue Jul 6, 2021 · 14 comments
Closed

Crashing #22

seancarmody opened this issue Jul 6, 2021 · 14 comments

Comments

@seancarmody
Copy link

I tried installing cartogram3 on QGIS 3.20.0-Odense on MacOS 11.4. If I try to activate it QGIS crashes unceremoniously
@christophfink
Copy link
Contributor

christophfink commented Jul 6, 2021 •
edited
Loading

Thanks for the report. I don’t have recent Apple hardware, which means I cannot try to reproduce the crash.
Could you start QGIS from a Terminal window (its path is /Applications/GIS/QGIS.app/Contents/MacOS/QGIS) and copy & paste the output (possibly minus personal information).
Thanks!

@seancarmody
Copy link
Author

seancarmody commented Jul 6, 2021 via email

@christophfink
Copy link
Contributor

Thanks!

I have a hunch of what might cause the segmentation fault (Python’s multiprocessing seems to be at odds with newer MacOS versions, in general), and how to try to fix it (move the entire implementation to threading.Threads).

It will take me a day or two to produce a test version of the plugin that includes the fix - it would be great if you could then be available to test it.

@seancarmody
Copy link
Author

seancarmody commented Jul 6, 2021 via email

@christophfink
Copy link
Contributor

(note to self): The trace looks very similar to this one: https://stackoverflow.com/questions/55686045/qt-application-crashes-on-macos-at-launching

@christophfink
Copy link
Contributor

@seancarmody Just unearthed my oldish MacBook and found that I can run into the same error also on MacOS 10.15. Won’t need you on stand-by for testing is what I’m trying to say ;)

@seancarmody
Copy link
Author

Thanks!

@christophfink christophfink mentioned this issue Jul 7, 2021
Closed
@djwalkr
Copy link

djwalkr commented Sep 2, 2021

I have a similar issue with 3.20 as well as the nightly dev version on macOS. When the plugin is loaded the app crashes (as mentioned by seancarmody) but also upon recovery, adding any vector layer (raster and Lidar point data are unaffected) causes a crash if the CRS of the layer does not match the project CRS. It seems that the crash occurs just at the point where the "Select transformation" dialog would normally pop-up. I'm not sure if this helps the debug effort but thought I would add the info. Note that the LTR seems unaffected by the issue.

@christophfink
Copy link
Contributor

Thanks for reporting! At the moment this leaves me slightly more puzzled, but it will certainly help with debugging :)

@christophfink christophfink mentioned this issue Nov 23, 2021
Closed
@christophfink
Copy link
Contributor

Sorry this took such a long while - turned out I had to do a major rewrite.

Could you try whether this version works? (Install it via the option ‘Install from ZIP’ in the plugin manager)

Thanks!

@seancarmody
Copy link
Author

Thanks for the hard work - have successfully installed (I had to upgrade QGIS to 3.22 first) and will now try it out.

@christophfink christophfink mentioned this issue Dec 14, 2021
Merged
@djwalkr
Copy link

djwalkr commented Dec 16, 2021 via email

@seancarmody
Copy link
Author

I had a similar experience. I no longer get a crash or multiple instances firing up but I tried to create a cartogram on a Natural Earth map I already had open and it only got to 1% after about an hour

@seancarmody
Copy link
Author

Left it running overnight and it never got past 1%

@christophfink christophfink mentioned this issue Dec 17, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@seancarmody @christophfink @djwalkr