NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix
[Runtime Bug]: Halo CE Crashes on startup
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.7k
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Halo CE crashes on startup when using runtime versions 0.6.0 and above.
Regression
Introduced in Bridge commit 2b66ef0d109b6db3308ce1265a4f5354536529fd
Workaround
Temporarily resolve the issue by commenting out the following lines in bridge/src/client/d3d9_device.cpp:
gSwapChainMapMutex.lock();
gSwapChainMap[m_pSwapchain->getPresentationParameters().hDeviceWindow] = { m_pSwapchain->getPresentationParameters(), this->getCreateParams(), m_pSwapchain->getId()};
gSwapChainMapMutex.unlock();
How do you reproduce the bug?
Attempt to launch Halo CE with runtime versions 0.6.0 or above
Version
0.6.0 (logs are from 0.6.0)
Logs
halo_d3d9.log
NvRemixBridge.log
d3d9.log
Crash dumps
No .dmp files were generated
Media
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with bridge/src/client/d3d9_device.cpp and the regression commit 2b66ef0d109b6db3308ce1265a4f5354536529fd. Reproduce the startup crash with runtime 0.6.0, then inspect halo_d3d9.log, NvRemixBridge.log, and d3d9.log around the swap-chain map operations. Done means Halo CE starts without commenting out those lines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100