As described in the duplicate bug #1235209, this happens when an application tries to close itself. The application session is closed, destroying underlying mir surface resources, but then information about the destroyed surface (it's name) is requested leading to a crash. Still trying to get the details about why the name is requested.
As described in the duplicate bug #1235209, this happens when an application tries to close itself. The application session is closed, destroying underlying mir surface resources, but then information about the destroyed surface (it's name) is requested leading to a crash. Still trying to get the details about why the name is requested.