The implicitly-created GVariant is leaked in Service's volume_changed() function. We can fix it by making the variant explicit. But, should this be reported upstream as a Vala bug?
One line diff:
- volume_action.set_state (volume);
+ volume_action.set_state (new Variant.double (volume));
C code generated from "volume_action.set_state (volume)":
The implicitly-created GVariant is leaked in Service's volume_changed() function. We can fix it by making the variant explicit. But, should this be reported upstream as a Vala bug?
One line diff: action. set_state (volume); action. set_state (new Variant.double (volume));
- volume_
+ volume_
C code generated from "volume_ action. set_state (volume)":
static GVariant* _variant_new4 (gdouble value) { new_double (value)); sound_service_ volume_ changed (IndicatorSound Service* self, gdouble volume) { action_ set_state (volume_action, _tmp4_);
return g_variant_ref_sink (g_variant_
}
static void indicator_
...
_tmp3_ = volume;
_tmp4_ = _variant_new4 (_tmp3_);
g_simple_
...
}
C code generated from "volume_ action. set_state (new Variant.double (volume))":
static void indicator_ sound_service_ volume_ changed (IndicatorSound Service* self, gdouble volume) { new_double (_tmp3_); ref_sink (_tmp4_); variant_ unref0 (_tmp5_);
...
_tmp3_ = volume;
_tmp4_ = g_variant_
g_variant_
_tmp5_ = _tmp4_;
...
_g_
...
}