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.

Sign up for GitHub

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

Jump to bottom

why Gosemble runtime integrated in Substrate requires to grow the memory #7

Closed
2 tasks
radkomih opened this issue Dec 12, 2022 · 1 comment
Closed
2 tasks

why Gosemble runtime integrated in Substrate requires to grow the memory #7

radkomih opened this issue Dec 12, 2022 · 1 comment
Labels
question Further information is requested toolchain
Milestone
Phase 1 - M0 - Au...

Comments

@radkomih
Copy link
Collaborator

radkomih commented Dec 12, 2022 •
edited
Loading

  • why Gosemble runtime integrated in Substrate requires to grow the memory when its given 2048 pages?
  • heap_start for Gosemble runtime in Substrate Host - here
@radkomih radkomih changed the title Toolchain issues Toolchain issues and improvements Jan 3, 2023
@radkomih radkomih added this to the M0 - Auxiliaries milestone Jan 4, 2023
@radkomih radkomih changed the title Toolchain issues and improvements why Gosemble runtime integrated in Substrate requires to grow the memory Aug 30, 2023
@radkomih radkomih added the question Further information is requested label Sep 5, 2023
@failfmi failfmi closed this as completed Jan 22, 2024
@failfmi
Copy link
Collaborator

failfmi commented Jan 22, 2024

Old issue, was with runtime which was pre-GC leaking

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested toolchain
Projects
None yet
Milestone
Phase 1 - M0 - Auxiliaries
Development

No branches or pull requests
2 participants
@radkomih @failfmi