You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using nethogs for years for my BusyTasks app. I recently discovered strange and flawed data and wondered whether it is my program or the nethogs backend. After further investigation I found that nethogs does not output correct data when it's being started before the network connections, it sometimes even crashed. Unfortunately I can't reproduce the crashes, but the data mining problem instead.
Steps for reproduction on Ubuntu 22.04 with recent nethogs version:
Disable automatic connecting of all network connections
Reboot OS and start "nethogs -Ca"
Connect network manually
Start another "nethogs -Ca" in a separate window
Compare the results
When automatically starting BusyTasks on login, there are two options as workaround:
Either use automatic connecting mode or restart BusyTasks after activating network connections.
I cannot determine if it's a problem with connection handling in the operating system itself. The bug may not occur in older Ubuntu releases.
Thanks for your support
The text was updated successfully, but these errors were encountered:
I first encountered it with 0.8.6 from the ubuntu repositories. This version even sometimes crashed when connecting/disconnecting, so I downloaded and compiled 0.8.7, which did not crash, but still shows questionable output.
I did not download and install the recent version from github because as far as I see there have not been any relevant commits.
I've been using nethogs for years for my BusyTasks app. I recently discovered strange and flawed data and wondered whether it is my program or the nethogs backend. After further investigation I found that nethogs does not output correct data when it's being started before the network connections, it sometimes even crashed. Unfortunately I can't reproduce the crashes, but the data mining problem instead.
Steps for reproduction on Ubuntu 22.04 with recent nethogs version:
When automatically starting BusyTasks on login, there are two options as workaround:
Either use automatic connecting mode or restart BusyTasks after activating network connections.
I cannot determine if it's a problem with connection handling in the operating system itself. The bug may not occur in older Ubuntu releases.
Thanks for your support
The text was updated successfully, but these errors were encountered: