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

[CURA-12190] Expand the circumstances under which we expect the C++ object to be gone. #974

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

rburema
Copy link
Member

@rburema rburema commented Oct 15, 2024

This was uncovered after caching, but might've existed before; that extra update function that's now within the try could also call the emitters, causing the same problem for which the existing try-catches where made.

…one.

This was uncovered after caching, but might've existed before; that extra update function that's now within the try could _also_ call the emitters, causing the same problem for which the existing try-catches where made.

CURA-12190
Copy link
Contributor

@wawanbreton wawanbreton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit scary, but ok 😬

@rburema
Copy link
Member Author

rburema commented Oct 16, 2024

A bit scary, but ok 😬

I think that's mostly a result from coupling a garbage collected language so tightly with a self-managed one, and then try to have objects that correspond to each other on both sides of that barrier managed by yet another system that has been known to have some bugs -- and then I come along and try to do caching 😓

@HellAholic HellAholic merged commit 1c95bb3 into 5.9 Oct 18, 2024
8 checks passed
@HellAholic HellAholic deleted the CURA-12190_fix_cache_crash branch October 18, 2024 14:27
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.

3 participants