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

Locate and eliminate memory leak in the vere king #7010

Closed
jalehman opened this issue Jun 6, 2024 · 6 comments
Closed

Locate and eliminate memory leak in the vere king #7010

jalehman opened this issue Jun 6, 2024 · 6 comments
Assignees

Comments

@jalehman
Copy link
Member

jalehman commented Jun 6, 2024

I'm almost certain that such a leak exists. @mopfel-winrux has the same suspicion, as does @pkova.

@mopfel-winrux
Copy link
Contributor

Whenever I shutdown my ship I get the following error I suspect it might be related

loom: external fault: 0x7fe6b4fd3bb8 (0x200000000 : 0x280000000)

Assertion '0' failed in pkg/noun/manage.c:1791

bail: oops
home: bailing out

@mopfel-winrux
Copy link
Contributor

Also when I boot back up I get a spam of
http request was cancelled by the runtime

@mopfel-winrux
Copy link
Contributor

Joes merge got rid of the swap leak but introduced a weird bug where my ram usage kept going up. I switched the docker image from alpine to ubuntu and this disappeared.

@joemfb
Copy link
Member

joemfb commented Jun 12, 2024

@mopfel-winrux my guess this dns-resolution requests queuing up endlessly. could try fixing that granularly, but my preference is just to finish urbit/vere#639.

@mopfel-winrux
Copy link
Contributor

Yea I'm still getting failed dns resolution. Was going to let it run for a while to get some performance benchmark. then possibly try it outside of startram and see if it still occurs

@pkova
Copy link
Collaborator

pkova commented Jul 11, 2024

Fixed as of urbit/vere#639.

@pkova pkova closed this as completed Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

4 participants