Author Topic: M1 macOS command-line invocation crashes  (Read 494 times)

JohnGivler

  • Junior Community Member
  • Posts: 7
  • Hero Points: 0
M1 macOS command-line invocation crashes
« on: September 29, 2023, 07:17:24 AM »
On various Apple M1 boxen running macOS Ventura & Sonoma, with mac-arm beta3's bin directory (a.k.a. /Applications/SlickEditPro2023Beta3.app/Contents/MacOS) on the PATH, invoking vs from the command line to edit 1-or-more files always crashes, with either "Bus error: 10" or "Segmentation fault: 11" (the choice seems random).  It does not matter whether the cited files exist, or not.  It does not matter whether I have VSLICK="+new", or not.  It does not matter if the process is launched in the foreground, or in the background.

Example
vs *Html*.[ch]pp &
(a window flashes on-screen & instantly disappears)
Bus error: 10

I routinely use the command line to specify which files to load & perhaps edit, and my primary system is M1 Ultra, so this is a show stopper for me.

Nevertheless, my testing included other use cases, in which some things worked properly:
  • Invoking mac-arm beta3 vs without specifying any filenames works correctly (= starts without crashing, but with no editable file loaded), the same as clicking on the "s|e" icon (which also works).  The File dialog box works. 
  • Invoking mac-intel beta3 vs from the command line on a Monterey, Ventura, or Sonoma box with an Intel CPU works correctly, both with & without names of files-to-be-loaded. 
  • Invoking mac-intel beta3 vs from the command line on a Sonoma box with an M1 Ultra & Rosetta2 behaves identically with mac-arm beta3 vs on that box (= crashes iff a filename is given).
  • SlickEdit 27.0.2 works correctly (invoked from the command line, with or without filenames) on these same M1 and Intel macOS systems.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1818
  • Hero Points: 151
Re: M1 macOS command-line invocation crashes
« Reply #1 on: September 29, 2023, 12:54:38 PM »
I haven't reproduced it yet, but I'm still checking some things.

Can you look in the console app under Crash Reports, and see if there's an entry for SlickEdit?  If there is, post it, the stack trace may be enough to go by.

JohnGivler

  • Junior Community Member
  • Posts: 7
  • Hero Points: 0
Re: M1 macOS command-line invocation crashes
« Reply #2 on: September 29, 2023, 03:49:38 PM »
I have attached two (of many) vs crash reports, one for "Bus Error: 10" and the other for "Segmentation Fault: 11".  Both are for mac-arm beta3.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1818
  • Hero Points: 151
Re: M1 macOS command-line invocation crashes
« Reply #3 on: September 29, 2023, 04:13:16 PM »
Thanks, that's a big help.  I'll update if I find a workaround, but it will likely need to be a fix in the next drop.

Dennis

  • Senior Community Member
  • Posts: 3983
  • Hero Points: 517
Re: M1 macOS command-line invocation crashes
« Reply #4 on: October 05, 2023, 11:57:52 PM »
We believe we have a fix for the next drop.  Thanks for the patience and crash dumps.

florihupf

  • Community Member
  • Posts: 54
  • Hero Points: 0
Re: M1 macOS command-line invocation crashes
« Reply #5 on: October 31, 2023, 09:56:40 AM »
I think I run into the same crash with Slickedit 27.0.2 on Sonoma on a Mac.

Is there a way to get the same fix for 27.0.2 ?

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6919
  • Hero Points: 531
Re: M1 macOS command-line invocation crashes
« Reply #6 on: October 31, 2023, 02:39:42 PM »