GUI crash with cross-thread ownership exception when clicking alignment spots — Bruker timsTOF Pro 2 DDA-PASEF, IBF format, v5.5.260323

[mecolley]

I am reporting a GUI crash that occurs after successful processing of Bruker timsTOF Pro 2 DDA-PASEF data using IBF format in MS-DIAL v5.5.260323. Processing and alignment complete without error, but the alignment result viewer is non-functional and crashes on interaction.

Environment
MS-DIAL version: 5.5.260323
OS: Windows 10
RAM: 64 GB
CPU: Intel Xeon (8 cores / 16 logical processors)
Instrument: Bruker timsTOF Pro 2
Acquisition mode: DDA-PASEF
Input format: IBF (converted from .d via IbfConverter.exe bundled with MS-DIAL)

Inputs
3 lipidomics files (IBF) (1 QC, 1 Blank, 1 Sample)

Behavior
The blank filter has no visible effect on the dot plot
Clicking any spot in the dot plot triggers a crash
MS-DIAL becomes unresponsive and a crash report flashes on screen
The error message indicates a cross-thread ownership exception (approximately: "the calling thread cannot access this object because a different thread owns it")

Happy to provide data or additional information

[gauppj1]

I've got a preliminary follow up on the issue submitted by Ms. Colley. My run is similar to hers but only two files (sample and qc at about 20GB total) with 128GB of system memory. My run has been grinding in "Process alignment" for about 18 hours with around 80% memory used in the early going and 50% now.

I set up the application in Visual Studio referencing the 5.5 tag and captured the memory for my active process. I've attached a screenshot of the VS UI. It looks like unreferenced instances of RawPeakElement arrays are occupying the memory at roughly 44GB. Could be a memory leak or (very) delayed garbage collection. I couldn't say at the moment.

I'll try my hand at functional debugging after I get some familiarity with the objects and operations in alignment.