Repository navigation
Replies: 5 comments 1 reply
|
If you could reproduce this problem set this in config: env=ASAN_OPTIONS,detect_leaks=1:halt_on_error=0:log_path=/tmp/asan.log then rebuild mango use these command cd mango sudo rm build -r meson build -Dprefix=/usr/ -Dasan=true sudo ninja -C build install Once a memory leak occurs, it will automatically generate a report in /tmp/asan.log |
|
btw , which os your are using?? what is the output of mango -v? |
|
You can try the latest submission. I have made some optimizations |
|
@DreamMaoMao I tried the custom build for a while, it got around max 700-800MB yesterday. Then I switched to the new 0.17.2, and it's been stable around 120MB again today. I will keep monitoring and report back. |
|
@DreamMaoMao 0.17.2 seems to be stable, it's been around 100-120MB stable now. So I guess you fixed it 👍 |
Uh oh!
There was an error while loading. Please reload this page.
After some general internet browsing use I want outside, the PC auto-locked and suspended.
When I came back I woke the PC, but then I noticed the memory usage meter of Noctalia was in the red.
The Mango process (version 0.17.1) was using a whopping 18GB of memory. I did a quick re-log to fix that, and it stays around 113MB right now.
If it happens again next time, what can I do to create a useful issue with debug information? What do I provide?
All reactions