Photos use too many python processes
Bug #1169913 reported by
Michal Hruby
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Photos Lens |
Confirmed
|
High
|
David Callé | ||
| Unity |
Confirmed
|
High
|
Unassigned | ||
| unity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Atm photos scopes live each in a separate python process, this is very bad for performance / cpu usage / battery life and should be fixed asap.
| tags: | added: 100scopes |
| Changed in unity-lens-photos: | |
| importance: | Undecided → High |
| Changed in unity: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in unity-lens-photos: | |
| status: | New → Confirmed |
| assignee: | nobody → David Callé (davidc3) |
Revision history for this message
| James Henstridge (jamesh) wrote | #1 |
Revision history for this message
| Geoff Teale (tealeg) wrote | #2 |
To post a comment you must log in.
We might want to adjust the Python scope-runner script to help with this: the way it loads the Python script makes it difficult to do e.g. relative imports of other modules (presumably we still want to require all the scopes to be merged into a single source file).