maierfelix / maierfelix/tiny-rtx

Clicking "Maximise" button in Windows causes crash

Open
#2 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
100
Forks
8
PR merge metrics
No merged PRs in 30d

Description

```
file:///C:/tiny-rtx/src/utils.mjs:12
throw new Error(`Vulkan assertion failed with ${key}`);
^

Error: Vulkan assertion failed with VK_ERROR_OUT_OF_DATE_KHR
at ASSERT_VK_RESULT (file:///C:/tiny-rtx/src/utils.mjs:12:15)
at RayTracingDemo.VulkanApplication.drawDefaultFrame (file:///C:/tiny-rtx/src/VulkanApplication.mjs:126:3)
at RayTracingDemo.drawFrame (file:///C:/tiny-rtx/src/index.mjs:174:8)
at Timeout.drawLoop [as _onTimeout] (file:///C:/tiny-rtx/src/index.mjs:152:9)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! tiny-rtx@0.0.1 start: `node --experimental-modules ./main.mjs --verbose-log`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the tiny-rtx@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the VK_ERROR_OUT_OF_DATE_KHR assertion in src/utils.mjs:12 and the drawDefaultFrame call in src/VulkanApplication.mjs:126, then trace the frame loop in src/index.mjs. Reproduce the crash by maximising the Windows window and determine the expected resize behavior; done means maximising no longer terminates the application and drawing continues.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.