Ticket #10963 (assigned)
InstrumentView crash debug mode OSX
Reported by: | Owen Arnold | Owned by: | Roman Tolchenov |
---|---|---|---|
Priority: | critical | Milestone: | Release 3.5 |
Component: | GUI | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
- Open MantidPlot
- Open a workspace in the AutoTest directory, I used one of the inter runs
- Open the instrument view -> Crash
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 QtCore 0x000000011519c650 QMetaObjectPrivate::indexOfSignalRelative(QMetaObject const**, char const*, bool) + 64 1 QtCore 0x00000001151ac343 QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) + 483 2 org.mantidproject.MantidPlot 0x000000010f52f22f ProjectionSurface::ProjectionSurface(InstrumentActor const*) + 463 (ProjectionSurface.cpp:44) 3 org.mantidproject.MantidPlot 0x000000010f533987 ProjectionSurface::ProjectionSurface(InstrumentActor const*) + 35 4 org.mantidproject.MantidPlot 0x000000010f53576e Projection3D::Projection3D(InstrumentActor const*, int, int) + 66 (Projection3D.cpp:40) 5 org.mantidproject.MantidPlot 0x000000010f4ca09e InstrumentWindow::setSurfaceType(int) + 2840 (InstrumentWindow.cpp:374) 6 org.mantidproject.MantidPlot 0x000000010f4cac97 InstrumentWindow::setSurfaceType(QString const&) + 497 (InstrumentWindow.cpp:479) 7 org.mantidproject.MantidPlot 0x000000010f4c9107 InstrumentWindow::init(bool, bool, double, double, bool) + 1661 (InstrumentWindow.cpp:218) 8 org.mantidproject.MantidPlot 0x000000010f45cd01 MantidUI::getInstrumentView(QString const&, int) + 1821 (MantidUI.cpp:2023) 9 org.mantidproject.MantidPlot 0x000000010f45d0d4 MantidUI::showMantidInstrument(QString const&) + 42 (MantidUI.cpp:2054) 10 org.mantidproject.MantidPlot 0x000000010f45d449 MantidUI::showMantidInstrumentSelected() + 113 (MantidUI.cpp:2094) 11 org.mantidproject.MantidPlot 0x000000010f5e4e88 MantidUI::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 12940 (moc_MantidUI.cxx:510)
This doesn't affect the last stable release, so either the problem has been introduced since then, or the compilation without the optimisations is responsible in some way.
Change History
Note: See
TracTickets for help on using
tickets.