Skip to content
This repository has been archived by the owner on Oct 9, 2022. It is now read-only.

Potential memory leak #160

Closed
wi1dcard opened this issue Jul 24, 2021 · 0 comments
Closed

Potential memory leak #160

wi1dcard opened this issue Jul 24, 2021 · 0 comments

Comments

@wi1dcard
Copy link
Member

Other shadow instances are consuming only ~400MiB of memory. However the shadow after re-import consumed ~4GiB. I assume there's a memory leak in shadow.

RAM per shadow (in MiB):
image

RAM graph of the re-imported shadow:
image

CPU graph of the re-imported shadow:
image

Full logs of the re-imported shadow:
shadow-memory-leak-full.log
@wi1dcard wi1dcard mentioned this issue Jul 24, 2021
Open
@xiaoch05 xiaoch05 mentioned this issue Jul 27, 2021
Open
@hackfisher hackfisher closed this as not planned Won't fix, can't repro, duplicate, stale Jul 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hackfisher @wi1dcard