Skip to content

Conversation

@proost
Copy link
Contributor

@proost proost commented Aug 17, 2025

@allenss-amazon

I found missed part. there are interned string, but not stored in the store. but deallocation track all interned strings. so we should track only shared interned strings which are stored in the store.

Copy link
Member

@allenss-amazon allenss-amazon left a comment

Choose a reason for hiding this comment

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

I think this is the wrong strategy. We should less clever, not more clever. The underlying problem is that you're not including the owned, but not shared strings in stringpool. Why not? I think if you just wrap the constructor and destructor of the InternString object with another IsolatedMemoryScope, then you'll solve the problem. It will means that InternString object which aren't entered in the pool get counted in the overall stat. But I don't see that as a problem.

@proost proost requested a review from allenss-amazon August 18, 2025 14:59
…o fix-string-interning-store-memory-usage

Signed-off-by: proost <[email protected]>
@proost
Copy link
Contributor Author

proost commented Aug 18, 2025

@allenss-amazon
Yes. you are right. 21a20cc

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.

2 participants