TStream.Write causes kernel oblivion on Cosmos Userkit Body: I asked for a byte. The kernel gave me an existential crisis.

[jukereise]

Area of Cosmos - What area of Cosmos are we dealing with?

file i/o

Expected Behaviour - What do you think that should happen

an file read should happen

Actual Behaviour - What unexpectedly happens?

vm crashes

Reproduction - How did you get this error to appear?

do any reading/writing using streams

Version - Were you using the User Kit or Dev Kit? And what User Kit version or Dev Kit commit (Cosmos, IL2CPU, X#)?

userkit ,newest one

[LoxyMono]

Got the faulty code we can look at?

[9xbt]

There is no 2025 userkit, unless you built one yourself. Either way, this repo hasn't been touched in half a year, so I assume latest version.

[9xbt]

Also, explain yourself better.

[jukereise]

var entry = fs.CreateFile(@"0:\logtest.txt");
var stream = entry.GetFileStream();
stream.WriteByte(69); // Just write 'E'
stream.Close(); is the faulty code

[jukereise]

was asleep

[Melvovin]

I recommend using dev kit if you don't use System.IO but vfs only, this fixed some bugs for me.

[TheVogels]

Aren't you usually meant to use Dispose on Streams and not Close?