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

Fix failing vector digitizer on mac, trac#3487 #456

Merged
merged 1 commit into from
Mar 25, 2020

Conversation

nilason
Copy link
Contributor

@nilason nilason commented Mar 24, 2020

This fixes the trac#3487 issue with failing (segfault) vector digitizing on mac.

It is actually a fix for two independent issues:

  1. ctypes related. Ctypesgen generates incomplete py files. Addressed by adding compiler flag.
  2. render related. On mac a render cycle has already started when the toolbar is inserted. Addressed by temporarily suspend rendering.

The second fix affects all platforms, so should be tested on linux and windows.

Important fix, should be backported to 7.8.3 if accepted.

Update: the second issue was reported separately: trac#3652.
The issue trac#3472 is probably also addressed by the ctypesgen fix.

Update 2: the second issue, was probably caused by my personally built debug version of python. Reverting to standard python build, this is no longer an issue. The trac#3652 doesn't seem to be an issue anymore.

@nilason nilason changed the title Fix failing vector digitizer on mac, trac#3487 Fix failing vector digitizer on mac, trac#3487 and trac#3652 Mar 24, 2020
@petrasovaa
Copy link
Contributor

Thanks for looking into this. While I can't comment on the ctypes issue and I am ok with merging that, I think the other issue with rendering could be solved in better way. I can't replicate it on Linux, is the error exactly the same as in trac#3652? There has been a fix for this since then in #161, so I just want to make sure your traceback is the same. I think what's needed is to pass the original environment (determining the rendering size) correctly to OnRenderDone in render.py, so all rendering uses the same size.

@nilason
Copy link
Contributor Author

nilason commented Mar 25, 2020

Thanks for bringing the second issue up. After testing with standard python I removed that part of the PR. See updated comment above.
For my part this is now good to go.

@nilason nilason changed the title Fix failing vector digitizer on mac, trac#3487 and trac#3652 Fix failing vector digitizer on mac, trac#3487 Mar 25, 2020
@neteler neteler added the macOS macOS specific label Mar 25, 2020
@petrasovaa petrasovaa merged commit 5ec42aa into OSGeo:master Mar 25, 2020
@cmbarton
Copy link
Contributor

cmbarton commented Mar 25, 2020 via email

@nilason
Copy link
Contributor Author

nilason commented Mar 25, 2020

Thanks! To the best of my knowledge, this was the last critical fix (but one: #408) for mac specific bugs.

@nilason nilason deleted the fix-trac-3487 branch March 25, 2020 22:38
@neteler neteler added this to the 8.0.0 milestone Dec 9, 2021
@nilason nilason mentioned this pull request Apr 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
macOS macOS specific
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants