[Octave-bug-tracker] [bug #56270] Octave 5.1.0 is freeze-y/hang-y on macOS

[Andrew Janke]

Follow-up Comment #3, bug #56270 (project octave):

I think an appropriate tool to use is macOS' "Spindump" creator in the
Activity Monitor. This will sample the application and produce stacktraces of
where it's spending its time.

Here's one from a recent build of default:
https://github.com/octave-app/octave-app/files/2963108/octave-6.0.0-hang-on-close.spindump.zip

A couple from users reporting 5.1.0 hanging upon launch:
https://github.com/octave-app/octave-app/files/3088267/octave.5.1.0.hang.on.launch.spindumps.-.2019-04-16.zip

One from myself getting a hang on startup:
https://github.com/octave-app/octave-app/files/3088998/octave.5.1.0.beachball.on.startup.-.brewed.-.apjanke.-.spindump.txt.zip

All these spindumps look similar. Here's what I think is the relevant part of
the stacktrace:


1000  Vt102Emulation::sendKeyEvent(QKeyEvent*) + 974 (liboctgui.5.dylib +
169502) [0x10f3ad61e]
    1000  Emulation::sendData(char const*, int) + 68 (liboctgui.5.dylib +
232264) [0x10f3bcb48]
      1000  write + 10 (libsystem_kernel.dylib + 124666) [0x7fff7c2876fa]
       *1000  hndl_unix_scall64 + 22 (kernel + 133574) [0xffffff80002209c6]
         *1000  unix_syscall64 + 616 (kernel + 6308424) [0xffffff8000804248]
           *1000  write_nocancel + 218 (kernel + 5536122)
[0xffffff800074797a]
             *1000  ??? (kernel + 5536522) [0xffffff8000747b0a]
               *1000  ??? (kernel + 2884439) [0xffffff80004c0357]
                 *1000  VNOP_WRITE + 106 (kernel + 2940314)
[0xffffff80004cdd9a]
                   *1000  spec_write + 748 (kernel + 2983340)
[0xffffff80004d85ac]
                     *1000  ??? (kernel + 5598603) [0xffffff8000756d8b]
                       *1000  ??? (kernel + 5438214) [0xffffff800072fb06]
                         *1000  lck_mtx_sleep + 126 (kernel + 513278)
[0xffffff800027d4fe]
                            *1000  thread_block_reason + 175 (kernel + 558655)
[0xffffff800028863f]
                              *1000  ??? (kernel + 562810)
[0xffffff800028967a]
                                *1000  machine_switch_context + 205 (kernel +
1590749) [0xffffff80003845dd]


Looks like it's stuck somewhere in the I/O routines for handling keyboard
input?

Downstream issues in Octave.app for this:
https://github.com/octave-app/octave-app/issues/24
https://github.com/octave-app/octave-app/issues/23

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56270>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/