WQM work unit has leaked/freed a lock

[falkorotter]

Hello,

Whenever we install an IPM module with a more complex dependency graph, we consistently encounter the error listed below originating from the method ##class(%IPM.Utils.Module).LoadModuleReference().

2025-12-29 13:57:40.492 | 12/29/25-12:57:29:587 (705) 2 [Utility.Event] ISCLOG: WorkMgr processwork: WQM work unit has leaked/freed a lock ns=KELVIN rtn=%SYS.WorkQueueMgr
data=$lb("lockdiff","-IRIS.WorkQueue(""Worker"",705),-IRIS.WorkQueue(""Group"",9350305239816)","function","S
%sc=##class(%IPM.Utils.Module).LoadModuleReference(.%p1,.%p2,.%p3,.%p4,.%p5,.%p6,.%p7)","group",9350305239816,"workidx",3,"type",2)2025-12-29 13:57:40.492 | 12/29/25-12:57:29:639 (705) 2 [Utility.Event] ISCLOG: WorkMgr startWork: WQM worker
has leaked/freed a lock during group work, shutting down ns=KELVIN rtn=%SYS.WorkQueueMgr data=$lb("lockdiff","-IRIS.WorkQueue(""Worker"",705)","group",9350305239816)

We haven't been able to pinpoint the exact dependency constellation triggering this issue yet. Are you aware of this problem, and do you have a solution or suggestions on how to further analyze it?

Our dev version is: IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2025.3 (Build 226U) Thu Nov 13 2025 12:40:31 EST

Best regards,

Falko

[isc-dchui]

I believe this is related to some known problems with async loading that we've removed in 0.10.5. If you're using an older version of IPM, you can use the -synchronous flag with the install command.