I've managed th confirm the problem repeatedly once using the automated
gui tests, but then the Mudlet window moved slightly and it didn't
happen again. I think it has to do with where you right-click...

(2) /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7f71589ba390]
(3) /home/vadi/Programs/Qt/5.7/gcc_64/lib/libQt5Widgets.so.5 
(QWidget::raise())) [0x7f715a4f9261]
(4) /home/vadi/Programs/Mudlet2/Github-Mudlet/src/mudlet() [0x616a79]
(5) /home/vadi/Programs/Mudlet2/Github-Mudlet/src/mudlet() [0x76b360]
(6) /home/vadi/Programs/Qt/5.7/gcc_64/lib/libQt5Core.so.5 
(QMetaObject::activate(QObject*, int, int, void**))) [0x7f71590ee716]

** Changed in: mudlet
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1674101

Title:
  Mapper: Custom exit lines crashes

Status in Mudlet:
  Confirmed

Bug description:
  Mudlet 3.0 Kappa
  Windows 10

  To reproduce it:
  In the mapper select a room, right mouse button click on the selected room. 
Choose "custom exit lines".

  Sometimes it works as intended and you can add a custom exit line.
  Sometimes the dialog box where you choose line properties does not popup.
  Sometimes Mudlet crashes.

  Checked with branch release_30 and still got the same problem. On
  discord I reported that it happens when selecting multiple rooms, that
  is not the case. It can happen while selecting one room too.

  #0  0x19c8d158 in QScopedPointer<QObjectData, 
QScopedPointerDeleter<QObjectData> >::data (this=0xbaadf011)
      at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
  #1  0x19871c50 in qGetPtrHelper<QScopedPointer<QObjectData> > (p=...)
      at ../../include/QtCore/../../src/corelib/global/qglobal.h:1014
  #2  0x19c7c48b in QWidget::d_func (this=0xbaadf00d) at 
../../include/QtWidgets/../../src/widgets/kernel/qwidget.h:124
  #3  0x198ac19c in QWidget::raise (this=0xbaadf00d) at kernel\qwidget.cpp:11696
  #4  0x0050ab43 in T2DMap::slot_setCustomLine (this=0x2c636540) at 
T2DMap.cpp:4543
  #5  0x005e30e1 in T2DMap::qt_static_metacall (_o=0x2c636540, 
_c=QMetaObject::InvokeMetaMethod, _id=32, _a=0x54ec398)
      at debug/moc_T2DMap.cpp:244
  #6  0x05deb9b1 in QMetaObject::activate (sender=0x34ea81e0, signalOffset=3, 
local_signal_index=1, argv=0x54ec398)
      at kernel\qobject.cpp:3730
  #7  0x05deb2f6 in QMetaObject::activate (sender=0x34ea81e0, m=0x19ce1000 
<_data_start__>, local_signal_index=1,
      argv=0x54ec398) at kernel\qobject.cpp:3595
  #8  0x198648c7 in QAction::triggered (this=0x34ea81e0, _t1=false) at 
.moc/debug/moc_qaction.cpp:369
  #9  0x19863b96 in QAction::activate (this=0x34ea81e0, event=QAction::Trigger) 
at kernel\qaction.cpp:1163
  #10 0x199f2791 in QMenuPrivate::activateCausedStack (this=0x35046180, 
causedStack=..., action=0x34ea81e0,
      action_e=QAction::Trigger, self=true) at widgets\qmenu.cpp:1130
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1674101/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~mudlet-makers
Post to     : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help   : https://help.launchpad.net/ListHelp

Reply via email to