Bug 25569 - unreproducible segfault when disposing a not prepared TpAccountManager instance
Summary: unreproducible segfault when disposing a not prepared TpAccountManager instance
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords: want-backtrace
Depends on:
Blocks:
 
Reported: 2009-12-10 14:31 UTC by Cosimo Alfarano
Modified: 2010-11-03 09:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cosimo Alfarano 2009-12-10 14:31:27 UTC
I've noticed that when I try to dispose an instance of TpAccountManager without preparing it, it shows the following:
  
(process:7055): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `TpAccountManager'

(process:7055): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed

(process:7055): tp-glib-CRITICAL **: tp_account_manager_is_prepared: assertion `TP_IS_ACCOUNT_MANAGER (manager)' failed


Depending on the situation, the process trying to dispose may segfault.
Comment 1 Simon McVittie 2010-05-03 03:31:43 UTC
Is this reproducible? If so, could you please enable fatal warnings (export G_DEBUG=fatal_warnings,fatal_criticals) and get a gdb stack trace for it?
Comment 2 Cosimo Alfarano 2010-05-07 03:55:18 UTC
I cannot reproduce it.

When I filed the bug, it was sufficient to _dup() _get_valid_accounts() without being prepared and g_object_unref() the AM to reproduce it, IIRC. When it happened, there were a good chance to segfault.

I couldn't reproduce the exact situation for it to segfault, though.
Comment 3 Simon McVittie 2010-11-03 09:43:42 UTC
Might this be a dup of Bug #31321?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.