-
Vlad Zahorodnii authored
Currently, testXdgForeign fails because imported and exported resources are destroyed immediately from destructor request handlers and code that performs cleanup in the exported-imported mapping tables accesses the dangling pointers. Previously, it wasn't an issue because the destruction of exported and imported resources was delayed using QObject::deleteLater().
bacec9f0