Found a new [actually very old] way to crash MusE!

MusE is a DAW for Linux with both MIDI and Audio editing. https://muse-sequencer.github.io

Moderators: MattKingUSA, khz, spamatica

Post Reply
User avatar
Impostor
Established Member
Posts: 1329
Joined: Wed Aug 17, 2022 1:55 pm
Has thanked: 137 times
Been thanked: 342 times

Found a new [actually very old] way to crash MusE!

Post by Impostor »

So, I set the global option "LV2 UI open behaviour" to "always ask".

With half of my LV2 plugins I then get a choice between two options. When both choices do actually open a GUI, I see no difference at all between them, but whatever. The problem is choosing one, then reopening the GUI with the other choice. Never fails to crash here.

Affected are Odin2, Pianoteq 7, LibreArp, Surge XT.

Attachments
GUI.png
GUI.png (17.18 KiB) Viewed 1265 times
Last edited by Impostor on Fri Jun 02, 2023 3:28 pm, edited 1 time in total.
User avatar
Impostor
Established Member
Posts: 1329
Joined: Wed Aug 17, 2022 1:55 pm
Has thanked: 137 times
Been thanked: 342 times

Re: Found a new way to crash MusE!

Post by Impostor »

As an example, I used Odin2 LV2, ran muse4 -D. The errors start when opening the GUI for the second time, with the other gui type. I first chose the kx type.

Code: Select all

Song::addNewTrack synth: idx:131 class:Odin2 label:Odin2 LV2
setRecord recordflag =0 f(record state)=0 autoRecEnable=1
setRecord recordflag =0 f(record state)=0 autoRecEnable=1
ACTIVE TOPWIN CHANGED to '<None>' ((nil))
ACTIVE TOPWIN CHANGED to 'Arranger' (0x5623926fa050)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5044, resource id: -1668576096, major code: 7 (ReparentWindow), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5045, resource id: -1668576096, major code: 7 (ReparentWindow), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5047, resource id: -1668576096, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5048, resource id: -1668576096, major code: 12 (ConfigureWindow), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5050, resource id: -1668576096, major code: 7 (ReparentWindow), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5053, resource id: -1668576096, major code: 1 (CreateWindow), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5054, resource id: -1668576096, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5055, resource id: -1668576096, major code: 19 (DeleteProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5056, resource id: 94372023, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5058, resource id: 94372023, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5059, resource id: -1668576096, major code: 8 (MapWindow), minor code: 0
The program 'muse4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 5057 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Segmentation fault (core dumped)
User avatar
Impostor
Established Member
Posts: 1329
Joined: Wed Aug 17, 2022 1:55 pm
Has thanked: 137 times
Been thanked: 342 times

Re: Found a new [actually very old] way to crash MusE!

Post by Impostor »

Turns out I get this crash with the 4.0 appimage too, so it's not a new bug.

Post Reply