Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MS-DIAL 5.5 Crashes During Alignment #481

Open
JohnFu4 opened this issue Dec 21, 2024 · 0 comments
Open

MS-DIAL 5.5 Crashes During Alignment #481

JohnFu4 opened this issue Dec 21, 2024 · 0 comments

Comments

@JohnFu4
Copy link

JohnFu4 commented Dec 21, 2024

Hello,

I am experiencing an issue where MS-DIAL 5.5 (and other versions 5.X) consistently crashes when I try to perform data alignment. These data work fine in MS-DIAL 4.9. Specifically, I can view features in individual samples; however, when I attempt to align all samples and view them together, the software crashes immediately.

I am using the following settings in MS-DIAL 5.5: proteomics mode, negative ion mode, with data measured in full scan mode on an LC-qTOF. The measured data are imported in mzML format.

In the Windows Event Viewer, I found the following report:

- 1026 2 0 0x80000000000000 1404124 Application CZBLKSYNTH660.cz.corporate.synthon-group.com - Application: MSDIAL.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArgumentNullException at CompMs.MsdialCore.Parser.MsdialProteomicsSerializer.LoadProteinResultContainer(System.String) at CompMs.App.Msdial.Model.Lcms.LcmsAlignmentModel..ctor(CompMs.App.Msdial.Model.DataObj.AlignmentFileBeanModel, CompMs.MsdialCore.Algorithm.Annotation.IMatchResultEvaluator`1, CompMs.MsdialCore.DataObj.DataBaseStorage, CompMs.App.Msdial.Model.Search.PeakSpotFiltering`1, CompMs.App.Msdial.Model.Search.PeakFilterModel, CompMs.MsdialCore.DataObj.DataBaseMapper, CompMs.MsdialLcmsApi.Parameter.MsdialLcmsParameter, CompMs.App.Msdial.Model.DataObj.FilePropertiesModel, System.Collections.Generic.List`1, CompMs.App.Msdial.Model.DataObj.AnalysisFileBeanModelCollection, Reactive.Bindings.Notifiers.IMessageBroker) at CompMs.App.Msdial.Model.Lcms.LcmsMethodModel.LoadAlignmentFileCore(CompMs.App.Msdial.Model.DataObj.AlignmentFileBeanModel) at CompMs.App.Msdial.Model.Core.MethodModelBase.LoadAlignmentFileAsync(CompMs.App.Msdial.Model.DataObj.AlignmentFileBeanModel, System.Threading.CancellationToken) at CompMs.App.Msdial.ViewModel.Lcms.LcmsMethodViewModel.LoadAlignmentFileCoreAsync(CompMs.App.Msdial.ViewModel.DataObj.AlignmentFileBeanViewModel, System.Threading.CancellationToken) at CompMs.App.Msdial.ViewModel.Core.MethodViewModel.LoadAlignmentFileAsync(System.Threading.CancellationToken) at CompMs.App.Msdial.ViewModel.Core.MethodViewModel+<>c__DisplayClass0_0.<.ctor>b__11() at Reactive.Bindings.AsyncReactiveCommand+<>c__DisplayClass6_0+<b__0>d.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Reactive.Bindings.AsyncReactiveCommand`1+d__16[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Reactive.Bindings.AsyncReactiveCommand`1+d__15[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at CompMs.App.Msdial.App.Main()

Thank you very much for your assistance.

@JohnFu4 JohnFu4 changed the title MS DIAL 5.5 Crushes during alingment MS DIAL 5.5 Crushes during alignment Dec 21, 2024
@JohnFu4 JohnFu4 changed the title MS DIAL 5.5 Crushes during alignment MS-DIAL 5.5 Crashes During Alignment Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant