google-research / google-research/falken

Hello Falken crash after run

Open
#32 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
275
Forks
37
PR merge metrics
No merged PRs in 30d

Description

Hello,

I followed the steps to have my environment setup. I have the service running, but when I try to run 'hello falken', I see the demo game loading and in a split second, it closes (crash).

I don't have any meaningful logs, but I can share what I have.

Execution Log:
`C:\falken-main\environments\cpp\hello_falken\build>.\Release\HelloFalken.exe
INFO: Starting game with brain_id and snapshot_id
INFO: Warning: Unable to set VSync! SDL Error: That operation is not supported
INFO: Not using vsync.
INFO: Connected to Falken!
INFO: Created brain: 6e2c585c-611b-4e59-927b-e378a0dd5d1d
INFO: Started session: 7b033385-d540-40b5-b2c9-05b2590795b0`

Event Viewer Error:
`Faulting application name: HelloFalken.exe, version: 0.0.0.0, time stamp: 0x6193ce7c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Faulting application path: C:\falken-main\environments\cpp\hello_falken\build\Release\HelloFalken.exe
Faulting module path: unknown`

Does anyone had this issue?

Is there a way for me to make this execution generate more info? (like a verbose mode?)

Contributor guide

Open the contributing guide

Research direction

The report points to environments/cpp/hello_falken/build/Release/HelloFalken.exe and records the launch command plus Windows exception 0xc0000005. Start by reproducing the crash in the C++ demo and inspecting the execution log and Event Viewer details. Done means identifying the reproducible crash cause and fixing it or adding useful diagnostic information.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.