Ralith / Ralith/hypermine

unexpected panic under load

Open
#494 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
202
Forks
22
Avg merge
6h 8m
Merged PRs (30d)
7

Description

while the host system was under heavy load, i encountered a panic. while i've lost the exact output, i noted the following:

  • nothing was printed before or after the panic
  • panicked at common/src/node.rs:77:25
  • 'no entry found for key'

(found while trying to reproduce some unexpected behaviour when killed by OOM)

Environment

  • CPU: Intel i7-8650U
  • GPU: Intel UHD 620 (integrated)
  • Memory: 6.5/7.3 GiB used
  • Swap: ~4/7.3 GiB used after OOM
  • Arch Linux, kernel 6.18.7.arch1-1
  • Sway (Wayland)

Steps taken before crash

  • write a client.toml config file containing only save = "/tmp/aaaa". no other config files present
  • /tmp/aaaa does not exist prior to launching the game
  • launch the game
  • open many firefox tabs, including a youtube video
  • start flying around ingame
  • youtube video starts playing
  • the panic occured about a second afterwards

Reproduction

i have been unable to reproduce this crash for ~15m of trying.

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 by inspecting common/src/node.rs:77:25 and determine which lookup can produce the reported “no entry found for key” panic. Review how the game handles the client.toml save path and memory pressure, then try to reproduce the crash under similar load. Done means the panic is understood and the relevant failure is handled or covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.