-
Notifications
You must be signed in to change notification settings - Fork 313
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
Version 1.7G: MEMORY LEAK, rrbb_new, new_count= Message #486
Comments
Thank you for reporting this. 73, John WB2OSZ |
WB2OSZ Hello. 73 JP3SRS |
Hi, I had similar issue on 3 of my setups.
Now testing with the fix. |
F4FXL - Were you using multiple radio channels? |
Only one channel. Direwolf crashed and restarted after approx 10 to 15 days. Yesterday I noticed that one of my digipeaters stopped sending its beacons to RF but was sending them to IS. I think it had just reached some erratic state before crashing. I checked the other digipeaters and noticed they had also restarted. I am running Direwold as a systemd service through tmux so the terminal output is lost when the service gets restarted upon crash. Edit: all of the digipeaters run with FX25 |
Thank you for that analysis. 73, |
I checked the VSS RSS in the ps command after starting direwolf. There was no change in VSS RSS in one week. The system is running stable. I think the volatile setting of the counter variable you described worked. Personally, I think it is fine to close it. 73 JP3SRS
|
To follow up on one previous message, it has been 2 weeks since I started direwolf.
The cacti graphs for the two weeks were also very stable. No more memory leak messages in my environment. Thank you very much. DE JP3SRS Masahiro Kusunoki |
Thank you for all of your testing and analysis. |
When running direwolf 1.7G, the following message started to appear continuously. It worked for about 7-10 days. This message was displayed on the terminal running direwolf.
There were no memory leak messages in the log file specified in direwolf.conf.
The execution environment is Raspberry Pi 4, 64-bit environment.
direwolf uses git cloned develop branch. and attach a .conf file.
direwolf -c d1296.conf -r 48000 -b 16 -d fff -d ii
I don't know the conditions to reproduce, and I'm building without the Debug option, so the only thing I can report as a problem is that the message occurred.
73 Masahiro Kusunoki JP3SRS
The text was updated successfully, but these errors were encountered: