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

slipstream-reports commented

2026-10-04 18:42:07 +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.0.7
Channel: Slipstream Beta
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
Settings:
  AlchemyRenderTonemapType = 0
  RenderDeferredSSAO = 1
  RenderDepthOfField = 0
  RenderFPSLimit = 0
  RenderFSAAType = 2
  RenderFarClip = 128
  RenderHiDPI = 0
  RenderMaxTextureResolution = 2048
  RenderMirrors = 0
  RenderQualityPerformance = 4
  RenderReflectionProbeDetail = 1
  RenderReflectionProbeLevel = 2
  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
  RenderVKUpscaler = 0
  RenderVSyncEnable = 1
  RenderVolumeLODFactor = 3
  UIScaleFactor = 1

Description

While using Slipstream, I logged in another account through the Firestorm viewer. After a few minutes of having both viewers open, Slipstream crashed suddenly, without giving any sort of error message.

Steps to reproduce

not given

_{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.0.7 Channel: Slipstream Beta 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 Settings: AlchemyRenderTonemapType = 0 RenderDeferredSSAO = 1 RenderDepthOfField = 0 RenderFPSLimit = 0 RenderFSAAType = 2 RenderFarClip = 128 RenderHiDPI = 0 RenderMaxTextureResolution = 2048 RenderMirrors = 0 RenderQualityPerformance = 4 RenderReflectionProbeDetail = 1 RenderReflectionProbeLevel = 2 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 RenderVKUpscaler = 0 RenderVSyncEnable = 1 RenderVolumeLODFactor = 3 UIScaleFactor = 1 ~~~ ### Description ~~~text While using Slipstream, I logged in another account through the Firestorm viewer. After a few minutes of having both viewers open, Slipstream crashed suddenly, without giving any sort of error message. ~~~ ### Steps to reproduce _not given_ --- <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-04 18:42:07 +00:00

Hemiva commented

2026-10-04 22:57:36 +00:00

I can also say that I was able to have two instances of Slipstream open at the same time in different accounts and didn't get any crash in the 10~20 minutes I used them for.

sky_line commented

2026-10-05 01:25:53 +00:00

Owner

Thanks for the report. Running Slipstream alongside Firestorm is supported on a best-effort basis: we'll look into problems it causes, but we can't guarantee compatibility with other viewers running at the same time. If it happens again, please attach your Slipstream.log (and the crash dump if one was written, from the logs folder). Logs help a lot, but no guarantees on a fix.

sky_line referenced this issue

2026-10-05 19:07:41 +00:00

[viewer] [crash] Crash: high ram usage and no rendering #458

sky_line commented

2026-10-05 19:07:41 +00:00

Owner

Possibly the same host-memory exhaustion as #458 (AMD, Windows; a 16 GB machine running two viewers). See the triage there. The fix in progress should help; please re-test on the next beta.

sky_line commented

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

Owner

Likely related to #462 (AMD on Windows, high memory while shaders compile). Fixed in 1.1.0 Beta 3; please retest on it.

Likely related to #462 (AMD on Windows, high memory while shaders compile). Fixed in **1.1.0 Beta 3**; please retest on it.

Hemiva commented

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

I suspect that the issue might have been releated to #465, since from what I remember, the Slipstream crash happened as soon as I closed a gesture editing window on Firestorm. Related to that, I can say that, on Beta 1.1.0.3, I could run both viewers at the same time and then close Firestorm, and Slipstream didn't have any issues and continued running normally.

I suspect that the issue might have been releated to #465, since from what I remember, the Slipstream crash happened as soon as I closed a gesture editing window on Firestorm. Related to that, I can say that, on **Beta 1.1.0.3**, I could run both viewers at the same time and then close Firestorm, and Slipstream didn't have any issues and continued running normally.

sky_line commented

2026-10-06 12:49:19 +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:14 +00:00

Hemiva commented

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

As written in #465:

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.

As written in #465: > 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 commented

2026-10-07 02:20:33 +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: the reporter can't reproduce this on 1.1.0 Beta 5, and the related fix landed in #462. Please reopen if it comes back.

sky_line closed this issue

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

Rows
Columns

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

System

Description

Steps to reproduce