On my Windows 10 and Windows 11 computers I am using Lightburn version 1.0.06. I have a Ruida controller selected but not actually connected to my laser.
Sometimes after closing Lightburn the process is still running, it shows in Task Manager and is using so much CPU that it almost makes my computer unusable. Sometimes there is even multiple Lightburn processes still running even though the application has been closed.
Anyone run into this and have a solution for it?
I haven’t seen this before. Does this happen on both of your computers?
Yes, happens on both computers but not every time I use lightburn. Have not found a reliable way to reproduce it.
Are either of you using a sync service, like Google Drive, OneDrive, iCloud, DropBox, etc on these files?
Ralph - Would you be comfortable following this to get me a stack trace of the one that’s hung?
I can’t guarantee it’ll get me what I need, but it’s worth a shot.
Yes, I always save to my Google drive.
It finally happened to me today, here is the stack trace for the process. Is this what you are looking for?
ntoskrnl.exe!KeSynchronizeExecution+0x5b66
ntoskrnl.exe!KeWaitForSingleObject+0x1460
ntoskrnl.exe!KeWaitForSingleObject+0x98f
ntoskrnl.exe!KeWaitForSingleObject+0x233
ntoskrnl.exe!ExWaitForRundownProtectionRelease+0x7dd
ntoskrnl.exe!KeWaitForSingleObject+0x3a29
ntoskrnl.exe!KiCheckForKernelApcDelivery+0x2b
ntoskrnl.exe!ExReleaseResourceAndLeaveCriticalRegion+0xc2
win32kbase.sys+0x44914
win32kfull.sys!NtHWCursorUpdatePointer+0x646
0x0000000000000000
win32u.dll!NtUserMsgWaitForMultipleObjectsEx+0x14
USER32.dll!MsgWaitForMultipleObjectsEx+0x9e
Qt5Core.dll!QEventDispatcherWin32::processEvents+0x394
qwindows.dll!qt_plugin_query_metadata+0x1dc9
LightBurn.exe+0x304f22
LightBurn.exe+0xde2a4
LightBurn.exe+0x3f3794
Qt5Core.dll!QMetaObject::activate+0x641
Qt5Widgets.dll!QAction::activate+0x10e
Qt5Widgets.dll!QAbstractButton::click+0x143
Qt5Widgets.dll!QAbstractButton::mouseReleaseEvent+0x8c
Qt5Widgets.dll!QToolButton::mouseReleaseEvent+0xf
Qt5Widgets.dll!QWidget::event+0xdc
Qt5Widgets.dll!QApplicationPrivate::notify_helper+0x140
Qt5Widgets.dll!QApplication::notify+0x7f3
Qt5Core.dll!QCoreApplication::notifyInternal2+0xb9
Qt5Widgets.dll!QApplicationPrivate::sendMouseEvent+0x3f3
Qt5Widgets.dll!QSizePolicy::QSizePolicy+0x2ab5
Qt5Widgets.dll!QSizePolicy::QSizePolicy+0xb45
Qt5Widgets.dll!QApplicationPrivate::notify_helper+0x140
Qt5Widgets.dll!QApplication::notify+0x1a97
Qt5Core.dll!QCoreApplication::notifyInternal2+0xb9
Qt5Gui.dll!QGuiApplicationPrivate::processMouseEvent+0x8c1
Qt5Gui.dll!QWindowSystemInterface::sendWindowSystemEvents+0x92
Qt5Core.dll!QEventDispatcherWin32::processEvents+0xde6
USER32.dll!CallWindowProcW+0x3f8
USER32.dll!DispatchMessageW+0x259
Qt5Core.dll!QEventDispatcherWin32::processEvents+0x5b0
qwindows.dll!qt_plugin_query_metadata+0x1dc9
Qt5Core.dll!QEventLoop::exec+0x1cb
Qt5Core.dll!QCoreApplication::exec+0x141
LightBurn.exe+0xaf8e
LightBurn.exe+0xb029
LightBurn.exe!FT_WriteEE+0x2ba934
LightBurn.exe!FT_WriteEE+0x2b99eb
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21
It is what I was asking for, but unfortunately it’s not telling me anything useful. Can you try turning on debug logging in the Help menu and shutting down, and if it hangs, kill it, then attach the LightBurnLog.txt file from your Documents folder? That might give me more info.
Do you have that SVG?
Yes, SendUDP is only available on Windows, however the LightBurn “listener socket” should be available on all platforms. SendUDP just sends a UDP command to localhost, port 19840 (and gets replies on port 19841).
Just noticed the lightburn process still running this morning, attaching log file.
LightBurnLog.txt (69.8 KB)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.