Issue 5824 in angleproject: Support Vulkan RenderDoc traces for Linux+Nvidia

59 views
Skip to first unread message

ti… via monorail

unread,
Apr 6, 2021, 9:52:54 PM4/6/21
to angleproj...@googlegroups.com
Status: Accepted
Owner: ----
CC: cnor...@google.com, ti...@google.com
OS: Linux
Priority: Medium
Renderer: Vulkan
Type: Defect

New issue 5824 by ti...@google.com: Support Vulkan RenderDoc traces for Linux+Nvidia
https://bugs.chromium.org/p/angleproject/issues/detail?id=5824

Using RenderDoc to trace an ANGLE capture is failing:

[ RUN ] TracePerfTest.Run/vulkan_command_and_conquer_rivals
Warning: setpriority failed in StabilizeCPUForBenchmarking. Process will retain default priority: Permission denied
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
WARN: driver_utils.cpp:177 (GetVendorString): ! Unimplemented: GetVendorString(../../src/libANGLE/renderer/driver_utils.cpp:177)
INFO: EGL ERROR: eglCreateWindowSurface: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../src/libANGLE/renderer/vulkan/RendererVk.cpp, selectPresentQueueForSurface:1842.
eglCreateWindowSurface failed: 0x3000
../../src/tests/perf_tests/ANGLEPerfTest.cpp:681: Failure
Failed
Failed initializing GL Window
[ FAILED ] TracePerfTest.Run/vulkan_command_and_conquer_rivals, where GetParam() = vulkan_command_and_conquer_rivals (627 ms)

driver_utils.cpp is upset because it doesn't recognize the vendor ID 0x10005.

Unfortunately, with that fixed it still doesn't work yet. Instead, SwiftShader can be used as a workaround:

$ VK_ICD_FILENAMES=~/code/chromium/src/third_party/angle/out/LinuxDebug/vk_swiftshader_icd.json ./build/bin/qrenderdoc

--
You received this message because:
1. The project was configured to send all issue notifications to this address

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

syous… via monorail

unread,
Apr 6, 2021, 10:38:56 PM4/6/21
to angleproj...@googlegroups.com
Updates:
Labels: Hotlist-Polish

Comment #1 on issue 5824 by syou...@chromium.org: Support Vulkan RenderDoc traces for Linux+Nvidia
https://bugs.chromium.org/p/angleproject/issues/detail?id=5824#c1

(No comment was entered for this change.)

Git Watcher via monorail

unread,
Apr 7, 2021, 11:25:09 AM4/7/21
to angleproj...@googlegroups.com

Comment #2 on issue 5824 by Git Watcher: Support Vulkan RenderDoc traces for Linux+Nvidia
https://bugs.chromium.org/p/angleproject/issues/detail?id=5824#c2

The following revision refers to this bug:
https://chromium.googlesource.com/angle/angle/+/6a60623171a66e791fd68bc3c6641ed7a786346f

commit 6a60623171a66e791fd68bc3c6641ed7a786346f
Author: Tim Van Patten <ti...@google.com>
Date: Wed Apr 07 01:55:47 2021

Add Mesa Vendor ID

ANGLE doesn't recognize the Mesa vendor ID, leading to a crash in
GetVendorString(). This is exposed when trying to capture traces of
ANGLE captures with RenderDoc.

Bug: angleproject:5824
Change-Id: I6c45a01dba78fa6057df26b38ca3db89cacf865e
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2809878
Reviewed-by: Cody Northrop <cnor...@google.com>
Reviewed-by: Jamie Madill <jma...@chromium.org>
Commit-Queue: Tim Van Patten <ti...@google.com>

[modify] https://crrev.com/6a60623171a66e791fd68bc3c6641ed7a786346f/src/libANGLE/renderer/driver_utils.cpp
[modify] https://crrev.com/6a60623171a66e791fd68bc3c6641ed7a786346f/src/libANGLE/renderer/driver_utils.h

cnort… via monorail

unread,
Oct 5, 2021, 6:28:03 PM10/5/21
to angleproj...@googlegroups.com
Updates:
Owner: ti...@google.com

Comment #3 on issue 5824 by cnor...@google.com: Support Vulkan RenderDoc traces for Linux+Nvidia
https://bugs.chromium.org/p/angleproject/issues/detail?id=5824#c3

Tim, is this fixed?

ti… via monorail

unread,
Feb 28, 2022, 3:59:03 PM2/28/22
to angleproj...@googlegroups.com
Updates:
Status: Fixed

Comment #5 on issue 5824 by ti...@google.com: Support Vulkan RenderDoc traces for Linux+Nvidia
https://bugs.chromium.org/p/angleproject/issues/detail?id=5824#c5


(No comment was entered for this change.)

Reply all
Reply to author
Forward
0 new messages