[viewer] [crash] Crash: Closing Firestorm made Slipstream crash immediately

slipstream-reports commented

2026-10-05 21:16:38 +00:00

Collaborator

Source: in-viewer report (Help > Report Bug)

Reporter (avatar name as given; not verified):

(not given)

Filed after a crash. Previous session ended with:

Previous session crashed (internal error)

System

Version: 1.0.1.1
Channel: Slipstream Release
OS: Microsoft Windows 11 64-bit (Build 22621.4317)
CPU: Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (2904.01 MHz)
Memory: 16314 MB
GPU: AMD Radeon RX 7600
GPU driver: 32.0.31041.1004
Vulkan: 1.4.349; ray tracing: enabled
Window: 1618x1000
Display: swapchain 1618x1000 BGRA8/sRGB fifo x3 (20 MB); monitors 1, window on 2560x1080@75Hz scale 1.00, HDR off
VRAM: n/a (no Vulkan world renderer)
Host memory: host-visible 36 MB / 16 allocs [cull 0/8 staging 33/2 readback 0/1 part 2/3 ui 1/2] device-only 415 MB | /s: alloc hv 0.0 (0 MB) dev 0.0 (0 MB), free hv 0.0 (0 MB) dev 0.0 (0 MB) | total allocs 133 fr
Settings:
  AlchemyRenderTonemapType = 0
  RenderDeferredSSAO = 1
  RenderDepthOfField = 0
  RenderFPSLimit = 0
  RenderFSAAType = 0
  RenderFarClip = 128
  RenderHiDPI = 0
  RenderMaxTextureResolution = 2048
  RenderMaxVideoMemoryMB = 0
  RenderMirrors = 0
  RenderQualityPerformance = 4
  RenderReflectionProbeCount = 128
  RenderReflectionProbeDetail = 1
  RenderReflectionProbeLevel = 2
  RenderReflectionProbeResolution = 128
  RenderScreenSpaceReflections = 0
  RenderShadowDetail = 2
  RenderTransparentWater = 1
  RenderVKAOStandard = 1
  RenderVKAlphaShadingRate = 0
  RenderVKGodRays = 0
  RenderVKOpaqueShadingRate = 0
  RenderVKProjectorShadows = 1
  RenderVKRayTracing = 1
  RenderVKRenderScale = 1
  RenderVKShadowResolution = 1024
  RenderVKSunShadows = 1
  RenderVKTAA = 0
  RenderVKTextureCompression = 4
  RenderVKUpscaler = 1
  RenderVSyncEnable = 1
  RenderVolumeLODFactor = 3
  UIScaleFactor = 1

Description

While having both Slipstream and Firestorm open, I closed Firestorm. Firestorm closed normally, but immediately after it did so, Slipstream closed abruptly, with no error message, window, or anything of sorts. Logging back on Slipstream, that was reported as a crash.

I don't know if that might be relevant, but each account was in a separate region.

Steps to reproduce

1. Open Slipstream, log in as one account.
2. Open Firestorm, log in as another account.
3. Quit Firestorm.

_{Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.}

**Source:** in-viewer report (Help > Report Bug) **Reporter** (avatar name as given; not verified): ~~~text (not given) ~~~ **Filed after a crash.** Previous session ended with: ~~~text Previous session crashed (internal error) ~~~ ### System ~~~text Version: 1.0.1.1 Channel: Slipstream Release OS: Microsoft Windows 11 64-bit (Build 22621.4317) CPU: Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (2904.01 MHz) Memory: 16314 MB GPU: AMD Radeon RX 7600 GPU driver: 32.0.31041.1004 Vulkan: 1.4.349; ray tracing: enabled Window: 1618x1000 Display: swapchain 1618x1000 BGRA8/sRGB fifo x3 (20 MB); monitors 1, window on 2560x1080@75Hz scale 1.00, HDR off VRAM: n/a (no Vulkan world renderer) Host memory: host-visible 36 MB / 16 allocs [cull 0/8 staging 33/2 readback 0/1 part 2/3 ui 1/2] device-only 415 MB | /s: alloc hv 0.0 (0 MB) dev 0.0 (0 MB), free hv 0.0 (0 MB) dev 0.0 (0 MB) | total allocs 133 fr Settings: AlchemyRenderTonemapType = 0 RenderDeferredSSAO = 1 RenderDepthOfField = 0 RenderFPSLimit = 0 RenderFSAAType = 0 RenderFarClip = 128 RenderHiDPI = 0 RenderMaxTextureResolution = 2048 RenderMaxVideoMemoryMB = 0 RenderMirrors = 0 RenderQualityPerformance = 4 RenderReflectionProbeCount = 128 RenderReflectionProbeDetail = 1 RenderReflectionProbeLevel = 2 RenderReflectionProbeResolution = 128 RenderScreenSpaceReflections = 0 RenderShadowDetail = 2 RenderTransparentWater = 1 RenderVKAOStandard = 1 RenderVKAlphaShadingRate = 0 RenderVKGodRays = 0 RenderVKOpaqueShadingRate = 0 RenderVKProjectorShadows = 1 RenderVKRayTracing = 1 RenderVKRenderScale = 1 RenderVKShadowResolution = 1024 RenderVKSunShadows = 1 RenderVKTAA = 0 RenderVKTextureCompression = 4 RenderVKUpscaler = 1 RenderVSyncEnable = 1 RenderVolumeLODFactor = 3 UIScaleFactor = 1 ~~~ ### Description ~~~text While having both Slipstream and Firestorm open, I closed Firestorm. Firestorm closed normally, but immediately after it did so, Slipstream closed abruptly, with no error message, window, or anything of sorts. Logging back on Slipstream, that was reported as a crash. I don't know if that might be relevant, but each account was in a separate region. ~~~ ### Steps to reproduce ~~~text 1. Open Slipstream, log in as one account. 2. Open Firestorm, log in as another account. 3. Quit Firestorm. ~~~ --- <sub>Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.</sub>

slipstream-reports added the

from-viewer

triage

labels

2026-10-05 21:16:38 +00:00

Hemiva referenced this issue

2026-10-05 22:20:08 +00:00

[viewer] [crash] Crash: sudden crash while running Firestorm simultaneously #402

Hemiva commented

2026-10-05 22:21:19 +00:00

I tried the steps again on Slipstream Beta 1.1.0.3, and Slipstream didn't crash this time. It's possible it might have been fixed.

I tried the steps again on **Slipstream Beta 1.1.0.3**, and Slipstream didn't crash this time. It's possible it might have been fixed.

sky_line commented

2026-10-06 12:49:20 +00:00

Owner

Thanks for the report! Since this was filed, we've shipped several stability and memory fixes. Two of them may be related:

runaway memory use on some systems (AMD/Windows especially);
better memory handling while graphics shaders compile.

Could you try the latest version and tell us whether it still happens?

Stable: 1.0.2
Beta: 1.1.0 Beta 4

Both are at https://slipstreamviewer.org/#download.

If it still crashes, please send a new report from Help > Report Bug after it happens. It now includes memory and graphics details that help us track it down.

Thanks for the report! Since this was filed, we've shipped several stability and memory fixes. Two of them may be related: - runaway memory use on some systems (AMD/Windows especially); - better memory handling while graphics shaders compile. Could you try the latest version and tell us whether it still happens? - **Stable:** 1.0.2 - **Beta:** 1.1.0 Beta 4 Both are at https://slipstreamviewer.org/#download. If it still crashes, please send a new report from **Help > Report Bug** after it happens. It now includes memory and graphics details that help us track it down.

sky_line added

priority

low

and removed

triage

labels

2026-10-06 12:49:20 +00:00

sky_line referenced this issue

2026-10-06 12:58:40 +00:00

Report Bug: follow up on an existing ticket (add a comment + logs) instead of always creating a new issue #486

sky_line added this to the Slipstream project

2026-10-06 15:04:13 +00:00

Hemiva commented

2026-10-06 16:57:19 +00:00

Using Beta 1.1.0.5. I left one instance of Firestorm and Slipstream open, did everything on Firestorm that previously made Slipstream crash, and Slipstream continued working with no crashes or any visible issues.

Using **Beta 1.1.0.5**. I left one instance of Firestorm and Slipstream open, did everything on Firestorm that previously made Slipstream crash, and Slipstream continued working with no crashes or any visible issues.

Hemiva referenced this issue

2026-10-06 16:59:08 +00:00

[viewer] [crash] Crash: sudden crash while running Firestorm simultaneously #402

Hemiva commented

2026-10-07 02:20:22 +00:00

I haven't been able to replicate this in a while. Unless someone else crashes Slipstream in a similar fashion, I suggest closing this issue for now.

sky_line commented

2026-10-07 22:01:01 +00:00

Owner

Closing as cannot-reproduce: the reporter can't reproduce it on 1.1.0.3 or 1.1.0.5. Please reopen if it comes back.

sky_line closed this issue

2026-10-07 22:01:02 +00:00

Rows
Columns

[viewer] [crash] Crash: Closing Firestorm made Slipstream crash immediately #465

System

Description

Steps to reproduce