Bug 10316 - Vivante: Memory corruption in wayland client process after hiding window
Summary: Vivante: Memory corruption in wayland client process after hiding window
Status: RESOLVED WONTFIX
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-fsl-arm (show other bugs)
Version: 2.1.2
Hardware: Other arm
: Low normal
Target Milestone: Future
Assignee: Tom Hochstein
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-09-21 14:28 UTC by Wieland Hagen
Modified: 2019-01-31 19:09 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Testcase app (3.76 KB, application/gzip)
2016-09-21 14:28 UTC, Wieland Hagen 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wieland Hagen 2016-09-21 14:28:20 UTC 
Created attachment 3436 [details]
Testcase app

See the attached testcase.

When hiding a wayland window by attaching a NIL-buffer to the wayland surface, memory corruptions occur, which are visible later on by malloc assertions failing.

This is only reproducible when
- a shader program is used while rendering
- after attaching the NIL-buffer we call
    1. eglDestroySurface(display, surface)
    2. eglCreateWindowSurface(display, cfg, window, 0)
    3. eglMakeCurrent(display, surface, surface, context)
(this is what's happening in QtWayland when calling QWindow::hide() with the QtWayland backend)

The attached code shows the bug. Run like
  ./wayland_window_hide 100 bug
on a target device.

This code runs fine on intel or nvidia host machines.
Comment 1 prabhu 2016-09-21 17:30:40 UTC 
It is already fixed and it will be available in upcoming release. 5.0.11P8.6
Comment 2 Otavio Salvador 2016-09-21 17:37:07 UTC 
As explained by Prabhu, this will be fixed when the next BSP release is out.
Comment 3 Wieland Hagen 2016-09-22 13:39:59 UTC 
That's good to hear. When will 5.0.11P8.6 be released? Is there already a change-log for the fixed issues?

And in case it's not possible for us to use a new yocto release, is it possible to use the new driver as a drop-in replacement for our system (kernel version 4.1.15-1.1.0+ga4d2a08)?
Comment 4 Ross Burton 2017-07-05 10:53:48 UTC 
Waiting For Upstream status is being removed, changing to Accepted.
Comment 5 Stephen K Jolley 2019-01-31 19:09:34 UTC 
bsps-meta-fsl-arm issues are now tracked in GitHub.  Please see: https://github.com/Freescale/meta-freescale