Repeated svcBreak crash in SaveMgrThread during autosave — Alpha 4.1

Open
  • Is something wrong?
#568 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
backend

Research direction

Start by reading the SaveMgrThread assertion and the save manager implementation; the issue provides a crash address and host backtrace but names no source files or tests. Compare autosaves from a fresh profile with the original save data to investigate what triggers the crash. Done means autosaving completes without the svcBreak crash for the reported save data.

Written by the indexing model from the issue text.

Description

bug
Before you start
Savage Wind version

0.4.1-alpha.4 (latest)

Game version

1.9.0

Your PC

Windows 11, Intel Core i7-9750H, NVIDIA GTX 1660 Ti Max-Q, 16 GB RAM.

Where in the game

Great Plateau

What happened, and how to make it happen again

Error: FATAL: svcBreak(reason=0) at 700267974c.

The logs indicate an SDK assertion failure in SaveMgrThread.

Steps and observations:

The game initially saved normally.

The crashes started after progressing through the first shrine, before obtaining the paraglider.

Loading older saves did not resolve the problem.

Creating a fresh save profile allowed several successful autosaves.

Copying the original save data to the new profile eventually reproduced the same crash.

The crash occurs while the game displays "Saving...".

Performance remains close to 60 FPS before the crash.

I can provide the crash log and save files for reproduction.

Is this a known issue with the save manager or save data implementation?

Settings

60 fps, 1080p, upscaler off

savagewind.log

[savagewind] Savage Wind 0.4.1-alpha.4 (commit 428d9cc, tree 976539b)
[gamelib] extracted/swgame.dll (game version 1.9.0, 87 sites)
[vk] gpu 0: NVIDIA GeForce GTX 1660 Ti with Max-Q Design (api 1.4.357)
[vk] driver: NVIDIA 621.14 (id 4), ASTC decoded on the CPU
[fs] mounted host directory C:\Users\User\Desktop\SavageWind-0.4.1-alpha.4-windows\Savage Wind\save_teste/save_0
[lm] D:/home/Cafe/U-King/trunk/Game/Lib/sead/engine/library/modules/src/basis/nin/seadRawPrintNin.cpp | PrintStringImpl | | SaveMgrThread | SDK has been aborted or failed assertion with no message.
FATAL: svcBreak(reason=0, info=722eb9e934, size=4) at 700267974c
host backtrace (guest functions are f_):
#0 00007ff60e3ef5d8 savagewind+af5d8
#1 00007ff60e34c0e1 savagewind+c0e1
#2 00007ff60e36ffc2 savagewind+2ffc2
#3 00007ff60e36bf52 savagewind+2bf52
#4 00007ffe8dd03721 swgame.dll+15e3721
#5 00007ffe8dcfb86e swgame.dll+15db86e
#6 00007ffe8dcfbbbf swgame.dll+15dbbbf

Before sending
  • This report contains no game files, keys, firmware, generated game code, save files or links to copies of the game.
Dominant language
C
Stars
811
Forks
37
Avg merge
17m
Merged PRs (30d)
13

Getting set up

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.

More from Revivedx/SavageWindRecomp

All issues in Revivedx/SavageWindRecomp

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.