Skip to content

Small Object Heap: code that allocates a lot of memory in SOH #2391

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

Closed
ht-s-fog opened this issue Mar 2, 2023 · 4 comments
Closed

Small Object Heap: code that allocates a lot of memory in SOH #2391

ht-s-fog opened this issue Mar 2, 2023 · 4 comments

Comments

@ht-s-fog
Copy link

ht-s-fog commented Mar 2, 2023

Translation: "As StreamReadGroup does not support blocking data reading, I have to use while(true) {} to read data, which will result in the following problems."

WX20230302-232406@2x

“Small Object Heap: code that allocates a lot of memory in SOH” is an unstable factor, how can I solve this problem?

@mgravell
Copy link
Collaborator

mgravell commented Mar 2, 2023

Are you in a tight loop without any delays? Because, sure that will allocate - maybe add a pause i.e. await Task Delay(...); ?

@ht-s-fog
Copy link
Author

ht-s-fog commented Mar 3, 2023

My requirement is that messages are processed promptly, so adding delays arbitrarily is not acceptable as it may lead to unexpected issues.

@NickCraver
Copy link
Collaborator

@ht-s-fog This isn't a scenario we support today, you can keep an eye on #1961, but we have no planed work/ETA there.

@NickCraver
Copy link
Collaborator

Closing out since #1961 is tracking blocking

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

No branches or pull requests

3 participants