https://bugs.winehq.org/show_bug.cgi?id=31207 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |7ae35a04f4dbc4284a69cfc1fef | |9dfbeb225e2b0 Summary|Monogram GraphStudio |Monogram GraphStudio v0.3.x |crashes when using |crashes when using |Graph->Insert Filter |Graph->Insert Filter --- Comment #8 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, this was fixed by commit https://source.winehq.org/git/wine.git/commitdiff/7ae35a04f4dbc4284a69cfc1fe... ("winegstreamer: Zero-initialize the GstImpl filter."), part of Wine 3.3 release. Thanks Zeb. There are a number of winegstreamer commits in between Wine 3.2 and 3.3. That one was specifically responsible for fixing the crash (just click the filter properties multiple times). --- snip --- $ git log --pretty=format:"%h - %an: %s" ^wine-3.2 wine-3.3 | grep gst 577fd01249 - Zebediah Figura: winegstreamer: Remove unused callbacks. 999c862f4f - Zebediah Figura: winegstreamer: Wait for GST_EVENT_CAPS instead of data. 7ae35a04f4 - Zebediah Figura: winegstreamer: Zero-initialize the GstImpl filter. c907d69cf0 - Zebediah Figura: winegstreamer: Avoid using the same event for multiple purposes. 9550556f3c - Zebediah Figura: winegstreamer: Use ERR instead of FIXME for GStreamer errors. 7bf59055cb - Zebediah Figura: winegstreamer: Make sure the pipeline state is NULL before removing output pins. 3201cee735 - Zebediah Figura: winegstreamer: Don't wait for the no-more-pads signal if playback fails. 2ea0d6ff81 - Zebediah Figura: winegstreamer: Check for failure from gst_element_set_state() instead of counting pads. 5374d5ca59 - Zebediah Figura: winegstreamer: Stop creating the filter if gstreamer fails to render. --- snip --- $ sha1sum graphstudio.exe a9e60ea3c1e18c6b2b8a2290b896eede3b355e7d graphstudio.exe $ du -sh graphstudio.exe 1.2M graphstudio.exe $ wine --version wine-3.2-198-g7ae35a04f4 $ wine --version wine-5.5-208-g3047385437 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.