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

[Andrew Janke]

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

I did a build of 5.1.0 with `--disable-readline`, and it built, with GUI. Ran
__run_test_suite__ and it had no more failures than usual for macOS. (4
failures; that's typical.)

I've been running it for a few hours, and no freezes, so I think it fixed the
freezing problem. That suggests the cause is indeed readline interaction.

I don't think we can use `--disable-readline` as a solution, though. The
Command Window in the GUI is pretty unusable with readline turned off: no
command history recall, the cursor position gets screwed up if you mouse-click
anywhere, and it frequently goes wonky and messes up its output or stops
responding for a while (without beachballing the app) and complaining about
unparseable inputs with what look like control characters.

> I thought if we disabled the gui if you do --no-line-editing that we would
have done the same globally if Octave was configured without readline. Should
we have done that?

I think that's a call as to whether you want to keep this mode around for
debugging purposes. I wouldn't want end users accidentally running in this
mode; it messes up the user interaction pretty badly. But it's been useful
here to narrow down the freezing problem.

    _______________________________________________________

Reply to this item at:

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

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