Julian Bouzas a824ae910f m-lua-scripting: only hold a strong reference of the Lua state when the script is enabled ... Scripts are always deactivated (and not finalized) before core disconnects, so we need to make sure the scripts don't hold a strong reference when creating them. They must only hold a strong reference of the Lua state if activated. In order to implement this properly, the lua_State has been wrapped into a GObject so that the 'lua-engine' construct-only property is a weak reference of the Lua state. Then, when the script is activated, a strong reference of the Lua state is held so the script can work. This strong reference is later dropped when the script is deactivated (right before the core is disconnected), avoiding leaked proxy warning messages in the log if a script has a global variable holding a proxy (Eg the alsa monitor in alsa.lua).		2026-06-01 07:37:02 -04:00
..
common	conf: refactor configuration loading	2024-03-04 07:07:56 +00:00
examples	tests/examples: add example on how to set node "params" under Props	2024-06-15 14:05:27 +03:00
modules	docs: fix various codebase typos Found via codespell -q 3 -S "*.po,./po/*,NEWS.rst" -L bootup,gir,inout	2025-01-28 15:45:54 +01:00
scripts	lib: settings: make settings name optional	2025-07-24 12:14:33 +03:00
wp	pipewire-object-mixin: Copy the props instead of wrapping them	2025-11-24 19:42:07 +02:00
wplua	m-lua-scripting: only hold a strong reference of the Lua state when the script is enabled	2026-06-01 07:37:02 -04:00
meson.build	tests/examples: add example on how to set node "params" under Props	2024-06-15 14:05:27 +03:00
script-tester.c	script-tester: wp_script_tester_create_stream(): fix property list leak	2025-07-29 09:18:46 +03:00