Look into this more `updateAcquireFence: Did not find frame.`
MV-GH opened this issue · 1 comments
MV-GH commented
Jerboa Version
0.0.69
Android Version + Phone
n/a
Describe The Bug
I have seen this a while in the output while running the application
updateAcquireFence: Did not find frame.
Unable to acquire a buffer item, very likely client tried to acquire more than maxImages buffers
updateAcquireFence: Did not find frame.
updateAcquireFence: Did not find frame.
Unable to acquire a buffer item, very likely client tried to acquire more than maxImages buffers
updateAcquireFence: Did not find frame.
Unable to acquire a buffer item, very likely client tried to acquire more than maxImages buffers
updateAcquireFence: Did not find frame.
Unable to acquire a buffer item, very likely client tried to acquire more than maxImages buffers
updateAcquireFence: Did not find frame.
Unable to acquire a buffer item, very likely client tried to acquire more than maxImages buffers
updateAcquireFence: Did not find frame.
updateAcquireFence: Did not find frame.
Unable to acquire a buffer item, very likely client tried to acquire more than maxImages buffers
updateAcquireFence: Did not find frame.
Unable to acquire a buffer item, very likely client tried to acquire more than maxImages buffers
updateAcquireFence: Did not find frame.
Unable to acquire a buffer item, very likely client tried to acquire more than maxImages buffers
updateAcquireFence: Did not find frame.
Initial research did not find anything usefull yet.
This might possibly be a problem. This did not happen a year ago.
Already tried using older coil and telephote libs, did not go away. Possible caused by compose update?
To Reproduce
Run app
check logs
In the case of a crash or when relevant include the logs
No response
MV-GH commented
This was fixed already.