-
Notifications
You must be signed in to change notification settings - Fork 326
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
Status Page: multiple data collection processes #2468
Status Page: multiple data collection processes #2468
Comments
I think I reproduced the behavior on an or750i on the current master. |
@herbetom and I met online sunday and dug into this issue. This is the current log in case someone wants to take this further:
On both 'bad' commits I was able to have processes gradually building up, which should not happen. We did so by having chromium run in background and waited for over an hour or so until it started to happen. Testing 'good' commits is unfeasible on such a small scale, I think. Eitherway, just wanted to leave this here, maybe we can go through options later. |
sse-multiplexd leaks pipe FDs to its child processes, so newer children keep the older ones alive when they should have received a SIGPIPE already fixes freifunk-gluon/gluon#2468
sse-multiplexd leaks pipe FDs to its child processes, so newer children keep the older ones alive when they should have received a SIGPIPE already fixes freifunk-gluon/gluon#2468
sse-multiplexd leaked pipe FDs to its child processes, so newer children keep the older ones alive when they should have received a SIGPIPE already. Closes freifunk-gluon/gluon#2468
sse-multiplexd leaked pipe FDs to its child processes, so newer children kept the older ones alive when they should have received a SIGPIPE already. Closes freifunk-gluon/gluon#2468
sse-multiplexd leaked pipe FDs to its child processes, so newer children kept the older ones alive when they should have received a SIGPIPE already. Closes freifunk-gluon/gluon#2468
reopen until packages repo got bumped in the modules file |
Bug report
What is the problem?
It can happen that Status Page data collection runs multiple times:
Screenshot-htop
It can be reproduced by opening multiple tabs of the status page. But it can also happen with just a single tab and some Browser foo.
The processes seem to accumulate and eventually all memory is used and there is a reboot.
Gluon Version:
Seen on Gluon master Branch for quite some time (quite possibly since the bump to 21.03). No reports regarding the last v2021.1.1 release.
Reports from the following devices:
The text was updated successfully, but these errors were encountered: