Percival
Percival
> You're not supposed to create `System` more than once. However this is intriguing, thanks for opening this issue! Emmmmmm,I mean when the `System` leaves its scope, its resources should...
> Yes it should, it's just that the issue isn't that critical considering that you're only supposed to have one `System`. I'll still try to fix the memory leak. Okay,...
I also observed this phenomenon,and I got the same result using `heaptrack`.In the future, I will pay attention to this problem as much as possible, if I find a solution,...
Wow!I have been wondering why there are eight threads running when I execute `let mut system = sysinfo::System::new_all();`, maybe it is also affected by `rayon`.
Yes,I used `let mut system = sysinfo::System::new();` instead, the situation returned to normal.
Currently, I have replaced glibc with musl-libc in the entire project. Consider adding a hint to the user in Rustdoc: describe the problem, and prompt the user to use musl...
Yes, I am pleasure to help users understand this problem and give a more detailed solution. I will open a PR within this week.
> You should **never** do that. `System` has been created to be created once and for all. System statistics are based on comparison with previous values, so it seems very...
> Did you find the root cause of the memleak? > There are AFAIK 2 problems here : > > * huge memory consumption due to libc threads (in rayon)...
Thanks for your report. Will fix in next version.