XWindow System Error when inserting plugins

[dguillemyn]

Bug:
On Raspbian Linux: inserting some plugins causes XWindow System Errors. This typically happens with more complex plugins, and is not necessarily depending on the plugin type (had problems with both LV2 and VST plugins). After the error is posted, JUCE throws assertions.
Below error dump when inserting CALF LV2 Equalizer plugin (note VST wrapper assertions when it is actually an LV2 plugin):

CALF DEBUG: instance 0x65ffa8 data (nil)
The program 'element' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
  (Details: serial 12867 error_code 10 request_code 130 minor_code 1)
  (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.)
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433

• To reproduce:
  Select a plugin and add it to the Graph Editor

• OS: Linux Raspbian: Linux raspberrypi 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l GNU/Linux (on Raspberry PI 4)

• Version: 0.45.1-9afdb1f6, build date: 15 Nov 202

• Standalone or Plugin
  Standalone

This might be related to issue #231.
Note that I applied the patch as referred to in issue 231

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[mfisher31]

Hello thanks for the report! Does it happen with LV2 plugins that don't have a UI?

[dguillemyn]

Hi,

Looks like I do have also issues with "UI less" LV2 plugins. I tried to insert a simple amplifier LV2 plugin resulting in an equal crash.
Note also that I have consistently XWindow system errors when I click the top left button(the one to keep the plugin on top of all other windows) of a plugin UI (that did successfully load) .
This is the crash dump:
`

(element:1922): Gdk-WARNING **: 20:10:14.481: GdkWindow 0x2400003 unexpectedly destroyed

(element:1922): Gdk-WARNING **: 20:10:14.527: GdkWindow 0x2400021 unexpectedly destroyed

(element:1922): Gdk-WARNING **: 20:10:14.604: GdkWindow 0x240001e unexpectedly destroyed
The program 'element' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 1225 error_code 9 request_code 130 minor_code 3)
  (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.)
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_Singleton.h:50
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433
JUCE Assertion failure in juce_VST_Wrapper.cpp:433

`
Note that sometimes Element simply aborts on startup (just with a "killed" notification on the console) but that's less frequent.
Perhaps I'm challenging too much my luck trying to run this on a RPI... On the other hand I've been running successfully Carla and Ingen on RPI 4, using various synths and FX plugins without issues, but I do like more Element in terms of usability and features ;)
As a last note: I compiled Element with the latest JUCE modules, but no avail, keeps on having the same problem.