Command key and move key

LightBurn Software Questions
1

When I use thé move key and accidently use thé command key rogether, il makes LightBurn shut down. On Mac mini as well on the laptop. Thé Mac mini isn’t connected to the laser and is used out of thé workshop for design.
Error message
Process: LightBurn [5160]
Path: /Applications/LightBurn.app/Contents/MacOS/LightBurn
Identifier: com.LightBurnSoftware.LightBurn
Version: 1.5.02 (1.5.02)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-02-28 18:28:27.0428 +0100
OS Version: macOS 14.2.1 (23C71)
Report Version: 12
Anonymous UUID: 91FCEC3C-925D-0C1D-8D81-50566A9C1AE5

Sleep/Wake UUID: D8E47258-C323-40D1-BF77-C4725CDBF583

Time Awake Since Boot: 24000 seconds
Time Since Wake: 1849 seconds

System Integrity Protection: enabled

Notes:
PC register does not match crashing frame (0x0 vs 0x10FBD86C3)

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [5160]

VM Region Info: 0 is not in any region. Bytes before following region: 4297850880
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
__TEXT 1002c0000-101a50000 [ 23.6M] r-x/r-x SM=COW …cOS/LightBurn

Error Formulating Crash Report:
Thx
Stef

2

What key specifically is the move key? Is this one of the arrow keys?

3

No, I mean the arrows in the move tab, to move the laser head

4

So anytime you hold command key while using any of the jogging buttons in Move window you get the crash?

5

Yes, I don’t do this intentionaly, but when I hold it by mistake, it should be the alt key to move by little encrements

7

This shouldn’t be a crash causing event.

In any case, I can’t reproduce this on an Intel Macbook Pro running 1.5.02. Holding CMD and pushing jogging controls does not crash for me.

Perhaps @Rick can take a closer look.

8

I am unable to reproduce this crash, provided the information supplied.

1 Like
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.