Started on-demand scopes are not shutted down
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
Critical
|
Thomas Strehl | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
After few hours without reopening the dash, I still have the scopes that were started by the server on demand running:
didrocks 3014 0.0 0.2 505932 16340 ? Sl 07:41 0:00 /usr/bin/python3 /usr/share/
didrocks 3019 0.0 0.2 505260 20852 ? Sl 07:41 0:00 /usr/bin/python3 /usr/share/
didrocks 3021 0.0 0.1 490484 15212 ? Sl 07:41 0:00 /usr/bin/python3 /usr/share/
didrocks 3025 0.0 0.2 505988 16480 ? Sl 07:41 0:00 /usr/bin/python3 /usr/share/
didrocks 3026 0.0 0.1 430984 15860 ? Sl 07:41 0:00 /usr/bin/python3 /usr/share/
didrocks 3031 0.0 0.2 505984 16476 ? Sl 07:41 0:00 /usr/bin/python3 /usr/share/
This is worrying as we are going to have potentially 40+ processes started on demand (all python), taking here 15/20 Mb of memory. As discussed previously, they should shut down after a period of inactivity.
tags: | added: 100scopes |
Changed in unity: | |
importance: | Undecided → Critical |
Changed in unity: | |
assignee: | nobody → Thomas Strehl (strehl-t) |
Changed in unity: | |
status: | New → Fix Released |
Changed in unity (Ubuntu): | |
status: | New → Fix Released |