-
Chun-wei Fan authored
In commit 8ff5668a, we are subscribing the GSettings backend later, but this meant that we need to initialize cache_lock earlier, as we might try to use that lock before a change notification is issued to subscribe the backend, which would then cause an access violation if we are trying to read GSettings values, as that lock is used to access the Windows Registry. Initialize cache_lock once we initialize the GSettings Registry backend, and delete it upon finalize, so that g_settings_read_from_backend() can proceed normally, even if the GSettings backend is not yet subscribed. https://bugzilla.gnome.org/show_bug.cgi?id=740413
f6bbd19b