This is a regression in Qt 5.12.5 (compared to Qt 5.12.4).

I attach a simple example project that triggers the behavior, but it can also be reproduced with the Qt example for qml framebuffer object.

To reproduce: run the application once, then close it and start it again.

Behavior: on the second run, the application crashes.  In the logs, we see:

I/DEBUG ( 101): pid: 10892, tid: 10905, name: qtMainLoopThrea >>> org.qtproject.example.test <<<I/DEBUG ( 101): !@dumpstate -k -t -z -d -o /data/log/dumpstate_app_native -m 10892I/ActivityManager( 382): Process org.qtproject.example.test (pid 10892) has died.D/Zygote ( 104): Process 10892 terminated by signal (11)

If I delete the application data and restart it works again one time, and crashes again on second startup.

This only happens on my Galaxy Tab 3.  Only seem to happen if we import a  QQuickFramebufferObject in the qml (not even need to actually instantiate it).