gwibber-service creates a new worker pool of threads/processes for each async request that it decided to do
Bug #624918 reported by
Tom "spot" Callaway
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Fix Released
|
Undecided
|
Ken VanDine | ||
gwibber (Ubuntu) |
Fix Released
|
Undecided
|
Ken VanDine |
Bug Description
In the latest gwibber trunk code, gwibber was causing the system to max out on available threads, specifically because gwibber-service was creating a new worker pool of threads/processes for each async request that it decided to do. Attached is a patch which resolves the issue, and does some minor cleanups.
Changed in gwibber: | |
assignee: | nobody → Ken VanDine (ken-vandine) |
Changed in gwibber: | |
milestone: | none → 2.32.0 |
status: | New → Triaged |
status: | Triaged → Fix Committed |
Changed in gwibber (Ubuntu): | |
assignee: | nobody → Ken VanDine (ken-vandine) |
Changed in gwibber: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I tried the patch, the only difference I've noted, is that loading has become slower.
Anybody else tried this?