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

Issue 1189 High memory footprint for DRC deck #1193

Merged
merged 10 commits into from
Nov 26, 2022
Merged

Conversation

klayoutmatthias
Copy link
Collaborator

No description provided.

Problem was that destruction of database objects was postponed during
callbacks, specifically the interpreter callback.

This caused db::Region objects to pile up.

The original feature was introduced to prevent issues when Ruby/C++
code interacts inside Qt UIs. The new fix does not disable GC, but
protects Ruby objects during method calls. Maybe that solves the problem too.
… after GC became active. Added a documentation hint.
@klayoutmatthias klayoutmatthias merged commit 1f2e8b4 into master Nov 26, 2022
@klayoutmatthias klayoutmatthias deleted the issue-1189 branch November 26, 2022 18:55
@gatecat
Copy link
Contributor

gatecat commented Nov 30, 2022

Thanks, this is working well for me locally. I'm wondering if it would be possible to get a release with this fix in too?

@klayoutmatthias
Copy link
Collaborator Author

klayoutmatthias commented Nov 30, 2022

Yes, there is.

I will release an additional 0.27.13 without that fix (stable branch - some important hot patches) and then 0.28 (target is in two weeks) with this fix.

Best regards,

Matthias

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

Successfully merging this pull request may close these issues.

None yet

2 participants