6 Crashes in 3 Days- MoveMouseCommand

[n1cholasv]

Body

Very cool program, and I'm loving it, but getting a little scared to use it due to frequency of crashes I seem to be inducing.

Steps to reproduce:

Not sure as it's intermittent.

Generally, active moving windows around, creating nodes, and moving between tile and carousel.

Complete crash and I need to restart and layout my windows again.

Any insights from the below?

Additional info

I was being very ambitious learning the tool and doing A lot of workspace and tile moving. Maybe I'm moving tiles around too quickly?

$ aerospace -v = aerospace CLI client version: 0.18.5-Beta 4213dfd9d958dbfe3f801e07d7d5af53303baa75

Console (4 of 6 crashes over 3 days were similar with runCmdSeq and MoveMouseCommand):

0 AeroSpace 0x1046ea4f4 specialized MoveMouseCommand.run(::) + 512
1 AeroSpace 0x1046dc2ed <deduplicated_symbol> + 1
2 AeroSpace 0x1046bc431 Array.runCmdSeq(::) + 1
3 AeroSpace 0x104716bcd closure #1 in closure #1 in onFocusChanged(:) + 1
4 AeroSpace 0x1046b49b1 <deduplicated_symbol> + 1
5 AeroSpace 0x10471bf61 specialized closure #1 in closure #1 in runSession(::body:) + 1
6 AeroSpace 0x1046b49b1 <deduplicated_symbol> + 1
7 libswift_Concurrency.dylib 0x286ccc461 TaskLocal.withValueImpl(:operation:isolation:file:line:) + 1
8 libswift_Concurrency.dylib 0x286ccc109 TaskLocal.withValue(:operation:isolation:file:line:) + 1
9 AeroSpace 0x10471aab1 specialized closure #1 in runSession(::body:) + 1
10 AeroSpace 0x1046b49b1 <deduplicated_symbol> + 1
11 libswift_Concurrency.dylib 0x286ccc461 TaskLocal.withValueImpl(:operation:isolation:file:line:) + 1
12 libswift_Concurrency.dylib 0x286ccc109 TaskLocal.withValue(:operation:isolation:file:line:) + 1
13 AeroSpace 0x104717f85 specialized runSession(:_:body:) + 1
14 AeroSpace 0x1047168e9 <deduplicated_symbol> + 1
15 AeroSpace 0x1046b43f5 <deduplicated_symbol> + 1
16 libswift_Concurrency.dylib 0x286d0083d completeTaskWithClosure(swift::AsyncContext*,

[nikitabobko]

The crash happens in move-mouse command inside your on-focus-changed callback. As a workaround you can temporarily stop using the feature

I am not yet 100% sure, but I think that your bug is the same as in #164 (even though the stacktraces are different). I'm going to do the release this weekend with the fix for the bug.

I'd like to ask you to try the release once it's released and report back