damloganza's profile

1 Message

 • 

78 Points

Sun, Nov 3, 2019 8:25 PM

Lightroom Classic: Thread stuck in loop - appears lua related

There appears to be an issue with my catalog. Opening it causes lightroom to immediately consume 12% (1 thread) of my CPU.

Being a developer I wanted to investigate, so I opened Process Explorer to see if I could find anything I could begin do about it. It appears there is a single thread that is at fault.

This is the stack trace I could get from Process Explorer:

wichitafoundation.dll!luaopen_WFSQLiteSetLogicImp+0xe96f4
wichitafoundation.dll!luaopen_WFSQLiteSetLogicImp+0xe8ff6
wichitafoundation.dll!luaopen_WFSQLiteSetLogicImp+0xd084b
wichitafoundation.dll!luaopen_WFSQLiteSetLogicImp+0xd5607
wichitafoundation.dll!luaopen_WFSQLiteSetLogicImp+0xd50ed
wichitafoundation.dll!luaopen_WFSQLiteSetLogicImp+0x97b20
wichitafoundation.dll!luaopen_WFSQLiteSetLogicImp+0x112917
AgKernel.dll!lua_getstack+0xa1d
AgKernel.dll!luaopen_table+0x3561
AgKernel.dll!lua_resume+0x294
AgKernel.dll!AgThrowProgramError+0x42
AgKernel.dll!lua_resume+0x33e
AgKernel.dll!luaopen_base+0x192c
AgKernel.dll!lua_getstack+0xa1d
AgKernel.dll!luaopen_table+0x3502
AgKernel.dll!lua_resume+0x294
AgKernel.dll!AgThrowProgramError+0x42
AgKernel.dll!lua_resume+0x33e
AgKernel.dll!luaopen_base+0x192c
AgKernel.dll!lua_getstack+0xa1d
AgKernel.dll!luaopen_table+0x3502
AgKernel.dll!lua_resume+0x294
AgKernel.dll!AgThrowProgramError+0x42
AgKernel.dll!lua_resume+0x33e
AgKernel.dll!luaopen_base+0x192c
AgKernel.dll!lua_getstack+0xa1d
AgKernel.dll!luaopen_table+0x3502
AgKernel.dll!lua_resume+0x294
AgKernel.dll!AgLua_callWithAutoReleasePool+0x39
AgKernel.dll!lua_getstack+0xa1d
AgKernel.dll!luaopen_table+0x3502
AgKernel.dll!lua_resume+0x294
AgKernel.dll!AgThrowProgramError+0x42
AgKernel.dll!lua_resume+0x33e
AgKernel.dll!lua_pcall+0x66
substrate.dll!AgMainThreadAction_trigger+0x672
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21


So it looks like there is something stuck in a loop in a lua script somewhere. I have disabled all plugins, so I don't think it's that, and I also tried creating a new empty catalog and it does not exhibit the issue, so it appears to be something with my catalog that is causing this.

I am able to suspend the thread and continue using Lightroom as normal, it appears unaffected by the suspended thread. Killing the thread seems to be a bad idea (as it would be), and caused Lightroom to not delete the catalog lock file on exit.

I am happy to provide more details if needed!

Responses

Employee

 • 

1.7K Messages

 • 

32.4K Points

2 y ago

To troubleshoot the problem, can someone post your Lightroom system info and follow https://forums.adobe.com/thread/925598 to collect the traceback log? Thanks in advance. And please also post your Lightroom system info Lightroom>Help>System Info...

Principal Scientist, Adobe Lightroom