epics> save_restore:write_save_file: Backup file (./autosave/auto_settings.savB) bad or not found. Writing a new one. [231004-221444]
dbpf 13SIM1:cam1:Acquire 1
DBF_STRING: "Acquire"
NDArrayPool:release ERROR, reference count < 0 pArray=0x7fa034009508
Thread SimDetTask (0x60000306dd40) can't proceed, suspending.
Dumping a stack trace of thread 'SimDetTask':
epics> [ 0x10883c300]: /Users/junkes/EPICS/epics-base/lib/darwin-x86/libCom.3.22.1.dylib(epicsStackTrace+0x70)
[ 0x10882d25e]: /Users/junkes/EPICS/epics-base/lib/darwin-x86/libCom.3.22.1.dylib(cantProceed+0xae)
[ 0x107195e97]: /Users/junkes/EPICS/epics-support/areaDetector/ADCore/lib/darwin-x86/libADBase.dylib(_ZN11NDArrayPool7releaseEP7NDArray+0x167)
[ 0x107120f82]: /Users/junkes/EPICS/epics-support/areaDetector/ADSimDetector/lib/darwin-x86/libsimDetector.dylib(_ZN11simDetector12computeImageEv+0x672)
[ 0x1071234a6]: /Users/junkes/EPICS/epics-support/areaDetector/ADSimDetector/lib/darwin-x86/libsimDetector.dylib(_ZN11simDetector7simTaskEv+0x156)
[ 0x1071247b9]: /Users/junkes/EPICS/epics-support/areaDetector/ADSimDetector/lib/darwin-x86/libsimDetector.dylib(_ZL8simTaskCPv+0x9)
[ 0x10883780b]: /Users/junkes/EPICS/epics-base/lib/darwin-x86/libCom.3.22.1.dylib(start_routine+0x14b)
[ 0x7ff8141381d3]: /usr/lib/system/libsystem_pthread.dylib(_pthread_start+0x7d)
[ 0x7ff814133bd3]: /usr/lib/system/libsystem_pthread.dylib(thread_start+0xf)
On 28. Sep 2023, at 15:59, Érico Nogueira Rolim <erico.rolim at lnls.br> wrote:
Hi,
If getting a traceback via a debugger is an option, then you can also attempt to set a watchpoint for the pNDArrayPool member of the NDArray object, in order to find out when it gets set to 0.
Cheers,
Érico
On 28/09/2023 10:18, Mark Rivers via Tech-talk wrote:
Hi Heinz,
Some questions:
- Have any images been collected before this error?
- What plugins are running?
- What happens if you disable all plugins before starting acquisition?
- Can you get a traceback when NDArray::release is called and NDArray.pNDArrayPool is 0?
Mark
Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.
Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.