Closed epengr closed 8 years ago
I noted which lines these seem to be related to a the moment … though the executable could have changed and a recompile could have happened since making the moc files incorrect. Looks like something to do with an alarm changed.
On Jan 21, 2015, at 3:31 PM, David Muir notifications@github.com wrote:
After looking up a report IDEAS AM crash, I was disheartened to notice several REIXS AM crashes that weren't reported to me. My users may be starting to think crashes are "normal" behavior:
/home/reixs/beamline/programming/acquaman/source/application/AMCrashMonitorSupport.cpp:132 sigaction.c:0 ??:0 ??:0 ??:0 /home/beamline/tools/qt/qt-4.7.3-SL54-x86_64/include/QtCore/qstring.h:883 /home/reixs/beamline/programming/acquaman/moc_AMControlEditor.cpp:184 reviewControlState() /home/reixs/beamline/programming/acquaman/moc_AMControl.cpp:253 end of alarmChanged() /home/reixs/beamline/programming/acquaman/moc_AMControl.cpp:136 alarmChanged() /home/reixs/beamline/programming/acquaman/moc_AMPVControl.cpp:78 some crazy qt qt_metacall error check /home/reixs/beamline/programming/acquaman/moc_AMPVControl.cpp:309 same as above for AMReadyOnlyWStatusControl /home/reixs/beamline/programming/acquaman/moc_AMPVControl.cpp:400 same as above for AMPVwStatusControl /home/reixs/beamline/programming/acquaman/moc_AMPVControl.cpp:488 same as above for AMPVwStatusAndUnitConversionControl /home/reixs/beamline/programming/acquaman/moc_CLSMDriveMotorControl.cpp:76 same as above for MDrive /home/reixs/beamline/programming/acquaman/moc_AMProcessVariable.cpp:222 end of alarmChanged() /home/reixs/beamline/programming/acquaman/moc_AMProcessVariable.cpp:129 alarmChanged() /home/reixs/beamline/programming/acquaman/moc_AMProcessVariablePrivate.cpp:338 near internalError /home/reixs/beamline/programming/acquaman/moc_AMProcessVariablePrivate.cpp:272 internal_onAlarmChanged() ??:0 ??:0 ??:0 /home/reixs/beamline/programming/acquaman/source/application/REIXS/REIXSMain.cpp:57 /home/reixs/beamline/programming/acquaman/source/application/AMCrashMonitorSupport.cpp:132 sigaction.c:0 /home/beamline/tools/qt/qt-4.7.3-SL54-x86_64/include/QtCore/qstring.h:883 /home/reixs/beamline/programming/acquaman/moc_AMScanView.cpp:211 /home/reixs/beamline/programming/acquaman/moc_AMScanView.cpp:623 /home/reixs/beamline/programming/acquaman/source/dataman/AMScanSetModel.cpp:519 /home/reixs/beamline/programming/acquaman/source/dataman/AMScanSetModel.cpp:358 /home/reixs/beamline/programming/acquaman/source/ui/AMCloseItemDelegate.cpp:146 ??:0 ??:0 ??:0 ??:0 ??:0 ??:0 /home/reixs/beamline/programming/acquaman/source/application/REIXS/REIXSMain.cpp:57 /home/reixs/beamline/programming/acquaman/source/application/AMCrashMonitorSupport.cpp:132 sigaction.c:0 /home/reixs/beamline/programming/acquaman/moc_AMSamplePlatePre2013View.cpp:275 ??:0 ??:0 ??:0 /home/reixs/beamline/programming/acquaman/source/application/REIXS/REIXSMain.cpp:57 /home/reixs/beamline/programming/acquaman/source/application/AMCrashMonitorSupport.cpp:132 sigaction.c:0 ??:0 ??:0 ??:0 ??:0 /home/reixs/beamline/programming/acquaman/source/ui/dataman/AMControlInfoListTableView.cpp:51 /home/reixs/beamline/programming/acquaman/source/ui/AMVerticalStackWidget.cpp:48 /home/reixs/beamline/programming/acquaman/source/ui/dataman/AMGenericScanEditor.cpp:286 ??:0 ??:0 ??:0 /home/reixs/beamline/programming/acquaman/source/application/REIXS/REIXSMain.cpp:57 /home/reixs/beamline/programming/acquaman/source/application/AMCrashMonitorSupport.cpp:132 sigaction.c:0 ??:0 ??:0 ??:0 ??:0 /home/reixs/beamline/programming/acquaman/source/ui/dataman/AMGenericScanEditor.cpp:286 ??:0 ??:0 ??:0 /home/reixs/beamline/programming/acquaman/source/application/REIXS/REIXSMain.cpp:57 And two empty reports...
— Reply to this email directly or view it on GitHub https://github.com/acquaman/acquaman/issues/1157.
It was reported to me a couple weeks ago that crashes are frequent when closing scans while another scan is running. This may or may not be related.
Aside from the issue that @helfrij is working on and the potential closing scans crashes, it seems like these crashes have thankfully/unfortunately/quantum mechanically gone away. I'm going to close this issue @epengr. If you find you find some more crashes then we'll make new issues like normal.
After looking up a report IDEAS AM crash, I was disheartened to notice several REIXS AM crashes that weren't reported to me. My users may be starting to think crashes are "normal" behavior:
And two empty reports...