LiveSplit / LiveSplit/LiveSplit
Live Split randomly stops executing
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.9k
- Forks
- 815
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 3
Description
This isn't a crash or anything, what happens is that at some point while playing livesplit seems to "disconnect" from the game, so it isnt able to read the game time or split. I tried using TraceSpy to readout what the output was and catch an error, putting print statements in init, exit, start, gameTime, reset, split, and update. The print statement in update also printed out the variables it should use, like game time and collected items. When the issue happens livesplit just stops updating altogether, it just stops getting to the print statements, "running split" being the last printed statement with nothing afterward. I don't think its the script, as other people use it without issue. I've tried reinstalling livesplit, and creating new splits and layout files, but the issue persists. I've also tried running livesplit as an admin just in case. The only error I get on tracespy is on livesplit start up and it is shown in the png below

This error might be unrelated or a non-issue, but at this point I have literally no idea what else to look into.
Edit: I'm also getting a different error when I open the game and the asl script starts:

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 by reproducing the freeze while tracing the ASL entry points named in the report: init, exit, start, gameTime, reset, split, and update. Compare the last successful call with the startup and game-open TraceSpy errors; done means LiveSplit continues reaching update and reading game time and splits after the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100