Assigned
Status Update
Comments
vi...@google.com <vi...@google.com> #2
agreed, i have 4/64 version and i have this shit bug.
aa...@gmail.com <aa...@gmail.com> #3
4/64 same here...
vi...@google.com <vi...@google.com> #4
+1
4/64 global version - black
4/64 global version - black
aa...@gmail.com <aa...@gmail.com> #5
4/64 same it's abysmal
aa...@gmail.com <aa...@gmail.com> #6
Same in Mi A2 4/64 with Emmc Micron
aa...@gmail.com <aa...@gmail.com> #7
4/64 same here...
Description
Another link I raised: https://issuetracker.google.com/issues/330066232
Version: From Android 14
Reproduce: AOSP build with x86_64, run with
then you will get error message like bellow
Why it failed from Android 14 as I described in https://issuetracker.google.com/issues/330066232 , from Android14, goldfish-opengl
AHardwareBuffer_lock() implementation is changed, once
cb->lockedUsage
is non-zero, it will reture error code. source code:device/generic/goldfish-opengl/system/hals/mapper3.cpp
However, in VTS GeneratedTestHarness.cpp MemoryDomain test, TestBlobAHWB object once is created, it will
map()
, then lock buffer inmap()
till testcase is end. If buffer is always lock, how vendor device get AHardwareBuffer virtual memory pointer. I checkframeworks/native/libs/nativewindow/include/android/hardware_buffer.h
, which seems I can only get virtual memory byAHardwareBuffer_lock()
, if it is locked by TestBlobAHWB object,AHardwareBuffer_lock()
returns fail.So I don't know how to get virtual pointer of CPU buffer.
Looking forward to your reply, thanks.