miral-app -launcher <app> sometimes causes egl image bad alloc
Bug #1723235 reported by
Brandon Schaefer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Invalid
|
High
|
Alan Griffiths |
Bug Description
When running the miral-app -launcher <app> script to start an app it causes issues egl image bad alloc:
ERROR: /home/bschaefer
Dynamic exception type: boost::
std::exception:
A way for me to reproduce is through an SDL2 app which:
miral-app -launcher ./testgl2 (from SDL2 source)
Causes flashing of the buffer rendering.
Changed in mir: | |
status: | Triaged → Invalid |
Changed in mir: | |
status: | Fix Committed → Invalid |
Changed in mir: | |
milestone: | none → 0.28.1 |
Changed in mir: | |
milestone: | 0.28.1 → none |
To post a comment you must log in.
This comes from a failed attempt to "bypass" a fullscreen surface from a Wayland client. Simply not bypassing for this case works around the issue:
- if (!native) EXCEPTION( std::invalid_ argument( "could not convert NativeBuffer")); flag_can_ scanout && flag_can_ scanout &&
- BOOST_THROW_
- if (native->flags & mir_buffer_
+ if (native && native->flags & mir_buffer_
But this loses efficiency.