Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot Run RenderDoc on Windows 10 (Application UI Window Does Not Open) #3488

Open
Cantersoft opened this issue Nov 19, 2024 · 3 comments
Open
Labels
Bug A crash, misbehaviour, or other problem Need More Info More information is needed from a user to work on this issue

Comments

@Cantersoft
Copy link

Description of Bug

No application user interface opens by opening the lnk shortcut, and no user interface opens by running any of the installed executables on Windows 10.0.19045.0, with the following hardware: AMD R9 7950X CPU, 64GB TEAMGROUP T-Force CARDEA memory, and RTX3090 GPU.

Although no window opens, the process qrenderdoc.exe starts, allocates a few MB of memory, and then remains stagnant. I am wondering if I'm missing some critical detail to the installation process. The app icons do not appear on the lnk shortcuts, either.

Steps to reproduce

Attempt to run the RenderDoc application on Windows 10.0.19045.0 from the Windows UI (i.e., double click on the lnk shortcuts, or directly on the executables in %programfiles%\RenderDoc.

Environment

  • RenderDoc version: Tested with installer and portable versions 1.31 and 1.35 (64-bit architecture)
  • Operating System: Windows 10.0.19045.0
  • Graphics API: XXX
@baldurk
Copy link
Owner

baldurk commented Nov 20, 2024

This sounds like some kind of system or 3rd party software problem, since if you have installed RenderDoc clean then I can't think of any bug that would cause it to fail. Do you have any kind of security software or anti-virus running? Could you try disabling those to see if they are causing the problem?

Have you tried attaching a debugger to the process, and use the symbol server - https://renderdoc.org/symbols - to resolve the symbols to see the callstack when it is failing? Or could you compile from source and see if that runs successfully?

@baldurk baldurk added Bug A crash, misbehaviour, or other problem Need More Info More information is needed from a user to work on this issue labels Nov 20, 2024
@Cantersoft
Copy link
Author

How does one attach a debugger to a process? I compiled RenderDoc locally, and the UI did open this time, though I am a little curious as to what the problem was with the precompiled versions.

@baldurk
Copy link
Owner

baldurk commented Nov 25, 2024

In visual studio you can attach to a process, the option is under the Debug menu.

If the problem is only with the precompiled versions then that points towards some security or anti-virus software being overly strict and causing problems with something not compiled locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A crash, misbehaviour, or other problem Need More Info More information is needed from a user to work on this issue
Projects
None yet
Development

No branches or pull requests

2 participants