Details
-
Technical task
-
Resolution: Done
-
P2: Important
-
None
-
None
-
2021wk38POAndroid&Mobile, 2021wk40POAndroid&Mobile, 2021wk42POAndroid&Mobile, 2021wk44POAndroid&Mobile, 2021wk46POAndroid&Mobile, 2022wk24FOQtforAndroid, 2022wk28FOQtforAndroid, 2022wk30FOQtforAndroid, 2022wk34FOQtforAndroid, 2022wk36FOQtforAndroid, 2022wk38FOQtforAndroid, 2022wk40FOQtforAndroid, 2022wk42FOQtforAndroid, 2022wk44FOQtforAndroid
-
970dadd763bffa086bc702ab93a367f6a788f40d (qt/qtmultimedia/dev) 46d5c59593534d614ec484c18f72d4e0c7c7c356 (qt/qtmultimedia/6.2)
Description
The declarative-camera example crashes when switching devices. It seems that after the disabling the camera and enabling it again, the new frame sent via
void QAndroidTextureVideoOutput::onFrameAvailable() {
...
m_sink->platformVideoSink()->newVideoFrame(frame);
}
is corrupted when received at qvideotexturehelper.cpp::updateUniformData(). Setting some custom QString field data into the frame before notifying and sending the frame, and printing it afterwards when received, prints a corrupted string.