Crash due to null assembly reference.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Release Type: Official Release
Version: 4.2.2293
Platform(s): Windows
Describe the bug
When the editor is trying to clear cache it seems to fail due to a null assembly.
To Reproduce
I can't properly reproduce it, I think it has to do with having the Editor open as well as VS2022 and both accessing the same file as the other. Im only basing that off of the behaviour being similar to a separate issue when debugging the source of Stride.
- Create any base project
- edit the project in VS
- reload assembly in stride
- hope it gets recreated
Log and callstacks
crash-log.txt
Contributor guide
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 with crash-log.txt and the assembly reload/cache-clearing path in the Stride editor, reproducing the reported sequence with VS2022 open if possible. Trace where the null assembly is encountered and use the call stack to identify the relevant code. Done means the reported reload scenario no longer crashes, with regression coverage where the failure can be reproduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100