diff options
| author | Niels De Graef <nielsdegraef@gmail.com> | 2023-01-16 19:15:20 +0100 |
|---|---|---|
| committer | Niels De Graef <nielsdegraef@gmail.com> | 2023-01-16 19:17:59 +0100 |
| commit | 0f04e5d371b8060801656715ea659e44fd8ebe9c (patch) | |
| tree | 9b3bf76e2f4b6360b3207492557763409036db70 /libsecret/secret-util.c | |
| parent | 33a4de59a2a3357cea5bd339489340a9c615024d (diff) | |
| download | libsecret-0f04e5d371b8060801656715ea659e44fd8ebe9c.tar.gz | |
Stop using GSlice
GLib is discussing deprecating/removing it upstream [1] since it has
only limited uses. Next to that, it seems to bork stack traces here when
using ASAN (for which you also have to specify `G_SLICE=always-malloc`
and some other envvars too).
In other words, let's just get rid of using `GSlice` and call the
allocation APIs directly.
[1]: https://gitlab.gnome.org/GNOME/glib/-/issues/1079
Diffstat (limited to 'libsecret/secret-util.c')
| -rw-r--r-- | libsecret/secret-util.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/libsecret/secret-util.c b/libsecret/secret-util.c index 4e6f2bb..092f40c 100644 --- a/libsecret/secret-util.c +++ b/libsecret/secret-util.c @@ -271,7 +271,7 @@ set_closure_free (gpointer data) SetClosure *closure = data; g_free (closure->property); g_variant_unref (closure->value); - g_slice_free (SetClosure, closure); + g_free (closure); } static void @@ -320,7 +320,7 @@ _secret_util_set_property (GDBusProxy *proxy, task = g_task_new (proxy, cancellable, callback, user_data); g_task_set_source_tag (task, result_tag); - closure = g_slice_new0 (SetClosure); + closure = g_new0 (SetClosure, 1); closure->property = g_strdup (property); closure->value = g_variant_ref_sink (value); g_task_set_task_data (task, closure, set_closure_free); |