[viewer] [crash] Crash: Crash upon teleporting to Lusk region #757
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#757
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! The log shows the crash happening right after arriving in a region, while the viewer was working out what is under the mouse pointer. 1.3.0 Beta 9 fixes a crash in exactly that spot (objects that had arrived but whose surface data had not loaded yet). Please update to Beta 9 and let us know whether it still happens. If it does, the next report will include more detail about what the viewer was doing at the moment of the crash.
Fixed in Slipstream 1.3.0 (stable): https://git.slipstreamviewer.org/sky_line/Slipstream/releases/tag/v1.3.0
If you still see this on 1.3.0, reply here and we'll reopen it.