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 a regression in JobSupport memory consumption #4110

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

dkhalanskyjb
Copy link
Contributor

Fixup to 65ef6ea: that commit made JobSupport consume more memory by making the information about whether a callback should be invoked when the job enters the cancelling state be represented as a boolean flag and not part of the object class hierarchy.

Now that flag is a virtual function instead.

Fixup to 65ef6ea: that commit
made `JobSupport` consume more memory by making the information
about whether a callback should be invoked when the job enters the
cancelling state be represented as a boolean flag and not part of
the object class hierarchy.

Now that flag is a virtual function instead.
@dkhalanskyjb dkhalanskyjb changed the title Fix increased memory consumption in JobSupport Fix a regression in JobSupport memory consumption Apr 22, 2024
Copy link
Collaborator

@qwwdfsad qwwdfsad left a comment

Choose a reason for hiding this comment

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

Thanks for spotting!

@dkhalanskyjb dkhalanskyjb merged commit 7353c11 into develop Apr 23, 2024
1 check passed
@dkhalanskyjb dkhalanskyjb deleted the dk-virtual-onCancelling branch April 23, 2024 09:28
Corje pushed a commit that referenced this pull request May 10, 2024
Fixup to 65ef6ea: that commit
made `JobSupport` consume more memory by making the information
about whether a callback should be invoked when the job enters the
cancelling state be represented as a boolean flag and not part of
the object class hierarchy.

Now that flag is a virtual function instead.
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