[viewer] [crash] Crash: Was just standing around and it crashed #599
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#599
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source: in-viewer report (Help > Report Bug)
Reporter (avatar name as given; not verified):
Filed after a crash. Previous session ended with:
System
Description
Steps to reproduce
not given
Log excerpt
Full scrubbed excerpt: slipstream-log-excerpt.txt
Last 40 lines
Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.
Thanks for the report and the log. Cause found: when video memory runs out (here when another app such as Discord takes some, or in busy places on 6-8 GB cards), a couple of buffer-resize and reflection-probe paths treated the failed allocation as fatal instead of backing off. Same root cause as #595, #597 and #599; a fix that makes these paths degrade quality instead of crashing is in progress.
Thanks for the report. This was filed from the 1.1.x release line. Slipstream 1.2 has a lot of changes in exactly this area (much lower video and system memory use, and crashes like this one turned into graceful slow-downs), so we're focusing on 1.2 rather than fixing 1.1.x. Please try the latest 1.2 beta (Preferences > Updates > Beta, or download it from slipstreamviewer.org), or wait for 1.2 stable. If it still happens on 1.2, a new report from the 1.2 viewer would help a lot.
Fixed in 1.2: running out of video memory now degrades quality instead of crashing (
649ca0dfa8,db76fc13ad). 1.2.0 stable is out (Preferences > Updates, or slipstreamviewer.org); please let us know if it still happens there. Moving to Testing until we hear back.Unable to test, currently crashing in launcher and on connecting to region in both 1.2 and 1.3.01
Noticing massive spikes in RAM usage to the point my system crawls, >98%
Fix shipped (v1.2.0-beta.8); this was filed from an older 1.1.x build and 1.2 reworked the area (out-of-memory now degrades instead of crashing). Closing as fixed; please open a new report from the current release if it still happens.