GpuMemoryBufferTrackerWin::Init() may crash on failure [399888623]

Fixed

Bug

Needs-Feedback

Status Update

No update yet.

Description

st...@microsoft.com

created issue #1

Mar 1, 2025 12:37AM

Microsoft Edge customers experience this crash in GpuMemoryBufferTrackerWin::Init() after CreateNV12Texture() fails by returning an empty handle. Afterwards, the invalid handle triggers a CHECK in GpuMemoryBufferHandle::set_dxgi_handle().

Callstack:

msedge!logging::CheckFailure+0x3
msedge!gfx::GpuMemoryBufferHandle::set_dxgi_handle
msedge!media::GpuMemoryBufferTrackerWin::Init
msedge!media::VideoCaptureBufferPoolImpl::ReserveForProducerInternal msedge!media::VideoCaptureBufferPoolImpl::ReserveForProducer msedge!media::VideoCaptureDeviceClient::ReserveOutputBuffer msedge!media::VideoCaptureDeviceMFWin::DeliverTextureToClient msedge!media::VideoCaptureDeviceMFWin::OnIncomingCapturedDataInternal
msedge!base::OnceCallback<void ()>::Run
...

Comments

su...@microsoft.com <su...@microsoft.com> Mar 4, 2025 12:29AM

Assigned to su...@microsoft.com.

su...@microsoft.com <su...@microsoft.com> Mar 5, 2025 03:43AM

Accepted by su...@microsoft.com.

ap...@google.com <ap...@google.com> #2Mar 5, 2025 08:13PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Radha Nakade <radhanakade@google.com>
Link: https://android-review.googlesource.com/3510337

Migrate traffic from pixel2 to mediumphone on FTL emulators.

Expand for full commit details

Migrate traffic from pixel2 to mediumphone on FTL emulators. 
 
Bug: 396715333 
 
Test: ./gradlew emoji2:emoji2-emojipicker:ftlmediumphoneapi33 
Change-Id: If5555443ca1a91479128e1bd6f4f909154c40ba2

Files:

M buildSrc/private/src/main/kotlin/androidx/build/FtlRunner.kt

Hash: c76f8094154101867327912e659ae47509755957
Date: Wed Feb 26 11:27:46 2025

su...@microsoft.com <su...@microsoft.com> Mar 5, 2025 09:07PM

Marked as fixed.

th...@google.com <th...@google.com> #3Mar 6, 2025 08:47AM

@Reporter, Could you please confirm if manual verification is needed ? If Yes, can you please provide detailed manual steps with screen-cast to verify the issue from our end.

Please help us in verifying the fix.

Thanks!

IssueTracker

This issue is a part of the Chromium tracker.