We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash to desktop
Another input fuzzer find. Switching to another tool via the number keys while dragging a control point leads to some fairly strange behavior.
In the video:
The editor crash setup sounds a bit contrived, but I think someone accidentally breaking undo/redo is believable.
2024.1009.1
logs.zip
The text was updated successfully, but these errors were encountered:
Steps 1 through 4 and 5 through 8 are independent scenarios and do not require one to precede the other.
First one is fixed by
diff --git a/osu.Game.Rulesets.Osu/Edit/Blueprints/Sliders/Components/PathControlPointVisualiser.cs b/osu.Game.Rulesets.Osu/Edit/Blueprints/Sliders/Components/PathControlPointVisualiser.cs index 70ccbdfdc4..97b0c84073 100644 --- a/osu.Game.Rulesets.Osu/Edit/Blueprints/Sliders/Components/PathControlPointVisualiser.cs +++ b/osu.Game.Rulesets.Osu/Edit/Blueprints/Sliders/Components/PathControlPointVisualiser.cs @@ -333,6 +333,9 @@ protected override void Dispose(bool isDisposing) base.Dispose(isDisposing); foreach (var p in Pieces) p.ControlPoint.Changed -= controlPointChanged; + + if (draggedControlPointIndex >= 0) + DragEnded(); } private void selectionRequested(PathControlPointPiece<T> piece, MouseButtonEvent e) @@ -473,7 +480,11 @@ public void DragInProgress(DragEvent e) EnsureValidPathTypes(); } - public void DragEnded() => changeHandler?.EndChange(); + public void DragEnded() + { + changeHandler?.EndChange(); + draggedControlPointIndex = -1; + } #endregion
Still investigating the second one since I'm not super sure what's going on there.
Sorry, something went wrong.
bdach
Successfully merging a pull request may close this issue.
Type
Crash to desktop
Bug description
Another input fuzzer find. Switching to another tool via the number keys while dragging a control point leads to some fairly strange behavior.
In the video:
The editor crash setup sounds a bit contrived, but I think someone accidentally breaking undo/redo is believable.
Screenshots or videos
crash2remux.mp4
Version
2024.1009.1
Logs
logs.zip
The text was updated successfully, but these errors were encountered: