Bug #805
Thread leak in frontend led to SIGABRT crash
| Status: | Closed | Start: | 01/25/2013 | |
| Priority: | Urgent | Due date: | ||
| Assigned to: |  Mirco Bauer |
% Done: | 100% |
|
| Category: | Frontend GNOME | |||
| Target version: | 0.8.10.2 | |||
| Complexity: | Medium |
Found in Version: | 0.8.11+git-0~186~oneiric1 |
|
| Votes: | 0 |
Description
Leaving the GNOME frontend running for a few days with a buggy internet connection led to a huge thread leak in the frontend till the Boehm GC crashed with "Too many root sets". See the attached crash log.
Associated revisions
Revision af9f70bcda72fde1852e4968f50c686dd8842eb3
[Frontend-GNOME] Fixed thread/memleak when reconnecting frontend (closes: #805, refs: #667)
Reconnecting to the smuxi-server was leaking all ChatView objects as
the ChatViewManager.ChatRemoved event was never raised from
ChatViewManager.Clear(). Thus StatusIconManager, NotifyManager and
IndicateManager continued to reference ChatViews objects. This leaked the
LastSeenHighlightQueue thread and probably also GTK+'s TextBuffer used in
MessageTextView.
Now we use the regular cleanup code of ChatViewManager.RemoveChat() instead.
History
Updated by Mirco Bauer 4318 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset af9f70bcda72fde1852e4968f50c686dd8842eb3.