[rhythmbox] rhythmdb: fix transfer annotation for rhythmdb_entry_new
- From: Jonathan Matthew <jmatthew src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [rhythmbox] rhythmdb: fix transfer annotation for rhythmdb_entry_new
- Date: Fri, 8 Aug 2014 13:53:35 +0000 (UTC)
commit 1569b882d22acc3ab9f964bfef85500b4c9aa551
Author: Jonathan Matthew <jonathan d14n org>
Date: Fri Aug 8 23:30:30 2014 +1000
rhythmdb: fix transfer annotation for rhythmdb_entry_new
rhythmdb_entry_new is a bit unusual in that the caller doesn't own a reference
to the newly created entry. This isn't really a problem as the caller is
responsible for deleting its own entries (or at least any callers going via
introspection are), and absent any other refcounting bugs, the entry will
stay alive until it is deleted.
This fixes crashes when deactivating the magnatune plugin, or when quitting
with the magnatune catalog loaded.
rhythmdb/rhythmdb.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/rhythmdb/rhythmdb.c b/rhythmdb/rhythmdb.c
index c9cce40..a37233f 100644
--- a/rhythmdb/rhythmdb.c
+++ b/rhythmdb/rhythmdb.c
@@ -1735,7 +1735,7 @@ rhythmdb_entry_insert (RhythmDB *db,
* This may return NULL if entry creation fails. This can occur if there is
* already an entry with the given uri.
*
- * Returns: the newly created #RhythmDBEntry
+ * Returns: (transfer none): the newly created #RhythmDBEntry
*/
RhythmDBEntry *
rhythmdb_entry_new (RhythmDB *db,
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]