Author Topic: slickedit pro 2018 crashes on MacBookPro during configuration  (Read 4921 times)

weiwen

  • Junior Community Member
  • Posts: 8
  • Hero Points: 1
Hi,

I just put slickedit pro 2018 on my MacBookPro (macOS Mojave version 10.14.4).  Slickedit always crashes during configuration.

Tools -> Quick Start Configuration

then click next on Welcome page, and then click next again on Emulation page.  Then Slickedit crashes everytime.

Slickedit still crashes after I remove folder "~/Library/Application Support/SlickEdit"

Any suggestion on how to solve the crash?

Thanks,
Weiwen

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 7131
  • Hero Points: 544
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #1 on: April 21, 2019, 09:04:55 PM »
Try downloading the latest binary from here https://www.slickedit.com/trial/slickedit.

While I haven't heard of this crash, there is a Mojave crash which was fixed where SlickEdit would crash when switching to Dark theme. Those who were already in Dark theme wouldn't see this crash.

weiwen

  • Junior Community Member
  • Posts: 8
  • Hero Points: 1
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #2 on: April 22, 2019, 01:34:57 PM »
I tried the latest binary.   Slickedit still disappears  after Emulation step.

SlickEdit Support

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 384
  • Hero Points: 29
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #3 on: April 22, 2019, 02:26:55 PM »
While we rarely ask a user to do this can you try a restart?

1.) Restart your machine.
2.) Remove  "~/Library/Application Support/SlickEdit"
3.) Run SlickEdit.

Any better?  Also, do you have any hardware peripherals plugged into your machine? (External number pads, external pens, touch pads?)

Thanks,
SlickEdit Support

weiwen

  • Junior Community Member
  • Posts: 8
  • Hero Points: 1
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #4 on: April 23, 2019, 04:48:06 PM »
I followed these steps.  SlickEdit still disappears after Emulation step.

The only external hardware is a Yubikey in a thunderbolt 3 port.

I attached gdb to slickedit process before it disappeared, and did not see anything in gdb window.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 7131
  • Hero Points: 544
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #5 on: April 23, 2019, 09:23:27 PM »
I think you need debug SlickEdit with lldb since on macOS, SlickEdit is built with clang.

Were you previously running SlickEdit on this macBook Pro before you updated the OS to 10.14.4? If so, did you previously have a Yubikey attached?

I'm running macOS 10.14.4 on my macMini.

weiwen

  • Junior Community Member
  • Posts: 8
  • Hero Points: 1
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #6 on: April 24, 2019, 03:08:50 AM »
This is a new machine, and this is first time to run SlickEdit on this laptop.

With lldb, I got following crash. 

* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
  * frame #0: 0x00007fff405c9d0d CoreFoundation`CFRelease + 109
    frame #1: 0x0000000105ef28b0 vs`seLineLayoutCache::getTextWidth(QFontMetrics*, bool, seCacheCell&, QPaintDevice*, bool, seCacheCell**, bool) + 880
    frame #2: 0x0000000105ef4570 vs`seLineLayout::drawLine(QPainter&, int, int, QRect const&, cmArray<seLineLayout::WidthToCursor>*, cmArray<seLineLayout::WidthToCursor>*, bool) + 1744
    frame #3: 0x0000000106040c0f vs`show_line(crt2_t*, int, QPainter*, int&, int&) + 2079
    frame #4: 0x000000010603a42e vs`crt2_refresh2(crt2_t*, QPainter*, QRect*, bool, bool, bool) + 4350
    frame #5: 0x00000001061600ae vs`refreshwindow(int, int*, QPainter*, QRect*, bool) + 6990
    frame #6: 0x000000010615e530 vs`se_refresh_window(filewindow_t*, int, QPainter*, QRect*, bool) + 96
    frame #7: 0x0000000105f57a77 vs`vsCtlEditorView::paint(QPaintEvent*) + 503
    frame #8: 0x0000000105f57832 vs`vsCtlEditorView::paintEvent(QPaintEvent*) + 210
    frame #9: 0x0000000109497e94 QtGui`QWidget::event(QEvent*) + 2116
    frame #10: 0x000000010944922d QtGui`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 557
    frame #11: 0x000000010944a843 QtGui`QApplication::notify(QObject*, QEvent*) + 403
    frame #12: 0x00000001091df2a1 QtCore`QCoreApplication::notifyInternal(QObject*, QEvent*) + 113
    frame #13: 0x0000000109492e17 QtGui`QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 1591
    frame #14: 0x00000001093e8ee9 QtGui`___lldb_unnamed_symbol204$$QtGui + 1881
    frame #15: 0x00007fff3dda9a6e AppKit`_NSViewDrawRect + 66
    frame #16: 0x00007fff3dd948b2 AppKit`-[NSView _drawRect:clip:] + 1752
    frame #17: 0x00007fff3dd93742 AppKit`-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1425
    frame #18: 0x00007fff3dd93afa AppKit`-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2377
    frame #19: 0x00007fff3dd93afa AppKit`-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2377
    frame #20: 0x00007fff3dd93afa AppKit`-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2377
    frame #21: 0x00007fff3dd93afa AppKit`-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2377
    frame #22: 0x00007fff3dd93afa AppKit`-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2377
    frame #23: 0x00007fff3dd93afa AppKit`-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2377
    frame #24: 0x00007fff3dd93afa AppKit`-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2377
    frame #25: 0x00007fff3dd93afa AppKit`-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2377
    frame #26: 0x00007fff3dd91794 AppKit`-[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 908
    frame #27: 0x00007fff3dd91fec AppKit`-[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 3044
    frame #28: 0x00007fff3dd913e2 AppKit`-[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 65
    frame #29: 0x00007fff3dd8ece4 AppKit`-[NSView _oldDisplayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 1893
    frame #30: 0x00007fff3dd8e31d AppKit`-[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 253
    frame #31: 0x00007fff3dd8af0e AppKit`-[NSView displayIfNeeded] + 1302
    frame #32: 0x00007fff3dd87c53 AppKit`-[NSWindow displayIfNeeded] + 280
    frame #33: 0x00007fff3dd87a94 AppKit`__NSWindowGetDisplayCycleObserverForDisplay_block_invoke + 684
    frame #34: 0x00007fff3dd82b88 AppKit`NSDisplayCycleObserverInvoke + 162
    frame #35: 0x00007fff3dd82708 AppKit`NSDisplayCycleFlush + 1030
    frame #36: 0x00007fff4b033ccb QuartzCore`CA::Transaction::run_commit_handlers(CATransactionPhase) + 49
    frame #37: 0x00007fff4b033413 QuartzCore`CA::Transaction::commit() + 213
    frame #38: 0x00007fff3dd820a1 AppKit`__65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274
    frame #39: 0x00007fff40657e88 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
    frame #40: 0x00007fff40657dbd CoreFoundation`__CFRunLoopDoObservers + 451
    frame #41: 0x00007fff405fa4d0 CoreFoundation`__CFRunLoopRun + 1136
    frame #42: 0x00007fff405f9e0e CoreFoundation`CFRunLoopRunSpecific + 455
    frame #43: 0x00007fff3f8e69db HIToolbox`RunCurrentEventLoopInMode + 292
    frame #44: 0x00007fff3f8e6715 HIToolbox`ReceiveNextEventCommon + 603
    frame #45: 0x00007fff3f8e64a6 HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 64
    frame #46: 0x00007fff3dc80ffb AppKit`_DPSNextEvent + 965
    frame #47: 0x00007fff3dc7fd93 AppKit`-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
    frame #48: 0x00000001093fc307 QtGui`___lldb_unnamed_symbol517$$QtGui + 615
    frame #49: 0x00000001091dc1f5 QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 581
    frame #50: 0x00000001060a624c vs`gui_modal_wait(filewindow_t*) + 108
    frame #51: 0x00000001060c146b vs`p_modal_wait_op() + 667
    frame #52: 0x0000000105ea20a3 vs`run_proc(int) + 195
    frame #53: 0x000000010621ce2f vs`execute_command(VSLSTR*, int, int*, slickedit::SEString const&) + 4991
    frame #54: 0x000000010621da0f vs`pshell_op() + 559
    frame #55: 0x0000000105ea20a3 vs`run_proc(int) + 195
    frame #56: 0x00000001060e913c vs`mac_first_init() + 44
    frame #57: 0x00000001078b1d31 vs`-[AppDelegate applicationDidFinishLaunching:] + 497
    frame #58: 0x00007fff4065daf6 CoreFoundation`__CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
    frame #59: 0x00007fff4065da70 CoreFoundation`___CFXRegistrationPost_block_invoke + 63
    frame #60: 0x00007fff4065d9da CoreFoundation`_CFXRegistrationPost + 404
    frame #61: 0x00007fff40665e88 CoreFoundation`___CFXNotificationPost_block_invoke + 87
    frame #62: 0x00007fff405ce8d4 CoreFoundation`-[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1642
    frame #63: 0x00007fff405cdc87 CoreFoundation`_CFXNotificationPost + 732
    frame #64: 0x00007fff42846217 Foundation`-[NSNotificationCenter postNotificationName:object:userInfo:] + 66
    frame #65: 0x00007fff3dc8781c AppKit`-[NSApplication _postDidFinishNotification] + 312
    frame #66: 0x00007fff3dc8716f AppKit`-[NSApplication _sendFinishLaunchingNotification] + 208
    frame #67: 0x00007fff3dc852c3 AppKit`-[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 552
    frame #68: 0x00007fff3dc84f13 AppKit`-[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 688
    frame #69: 0x00007fff4288fd6e Foundation`-[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 286
    frame #70: 0x00007fff4288fbeb Foundation`_NSAppleEventManagerGenericHandler + 102
    frame #71: 0x00007fff4181b397 AE`aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 1815
    frame #72: 0x00007fff4181ac29 AE`dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 41
    frame #73: 0x00007fff4181ab01 AE`aeProcessAppleEvent + 414
    frame #74: 0x00007fff3f8efec7 HIToolbox`AEProcessAppleEvent + 54
    frame #75: 0x00007fff3dc812f2 AppKit`_DPSNextEvent + 1724
    frame #76: 0x00007fff3dc7fd93 AppKit`-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
    frame #77: 0x00007fff3dc79eb0 AppKit`-[NSApplication run] + 699
    frame #78: 0x00000001093fc793 QtGui`___lldb_unnamed_symbol517$$QtGui + 1779
    frame #79: 0x00000001091dc1f5 QtCore`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 581
    frame #80: 0x00000001091df8dc QtCore`QCoreApplication::exec() + 188
    frame #81: 0x0000000105e1d666 vs`vmain(int, char**) + 2982
    frame #82: 0x000000010753725a vs`xmain + 42
    frame #83: 0x0000000105e3dae9 vs`main + 9
    frame #84: 0x0000000105deee34 vs`start + 52

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 7131
  • Hero Points: 544
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #7 on: April 24, 2019, 01:29:32 PM »
Thanks for the stack. It seems to be crashing in some Edit window text drawing code. It's not obviously exactly where in getTextWidth it's crashing (no obvious call to a Release function). This is a fairly large function. I'll have to think about how we can get more specific crash information on this (like a line number or something a lot closer to the actually problem).

What happens if you press ESC on the SlickEdit Quick start wizard at startup? I suspect if you open a file you will get the same crash. At least that's my guess.

weiwen

  • Junior Community Member
  • Posts: 8
  • Hero Points: 1
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #8 on: April 24, 2019, 02:44:06 PM »
You are right.  SlickEdit also crashes when opening a file.

If there is a build with better debugger symbols, I can repro and send better callstack.

Dennis

  • Senior Community Member
  • Posts: 3999
  • Hero Points: 522
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #9 on: April 24, 2019, 10:38:24 PM »
What locale are you running in on your MacBook?  I wonder if this is a problem where we fail to get a font that we expect.

SlickEdit Support

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 384
  • Hero Points: 29
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #10 on: April 25, 2019, 12:54:14 AM »
PM sent Weiwen.

weiwen

  • Junior Community Member
  • Posts: 8
  • Hero Points: 1
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #11 on: April 25, 2019, 01:13:31 AM »
output from locale:

LANG="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL=

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 7131
  • Hero Points: 544
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #12 on: April 25, 2019, 01:18:23 PM »
I've been testing the debug installer we sent you. It seems like LLDB has some sort of limitation where it won't show line numbers unless it finds the source code for it. I'll have to investigate this further to see if there is a workaround for this. If not, we will have to resort to adding printfs in the function.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 7131
  • Hero Points: 544
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #13 on: April 25, 2019, 04:57:43 PM »
While we're trying to figure out if we can get line numbers from LLDB we thought you should try changing the default edit window font.

Before opening any Editor window, try changing the font here:

Tools>Options>Appearance>Font>Unicode Source Windows

Choose something other than "Default Fixed Font".
« Last Edit: April 26, 2019, 01:46:05 AM by Clark »

SlickEdit Support

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 384
  • Hero Points: 29
Re: slickedit pro 2018 crashes on MacBookPro during configuration
« Reply #14 on: April 29, 2019, 12:42:01 PM »
PM sent to you Weiwen.

Regards,
SlickEdit Support