[Octave-bug-tracker] [bug #53521] GUI freezes and requires SIGKILL upon large pasted input

[Dan Sebald]

Follow-up Comment #5, bug #53521 (project octave):

No "screen" here.  I had to install "screen" to test your example, so I was
using the shell and octave-cli.

That copy/paste bug doesn't give me a warm fuzzy.  I use block copy via middle
mouse button all the time.

However, it could be that what I'm seeing (with the latest development
code...who knows, something could have been altered there in the last month)
is only a printout issue on Octave's part and not actually corrupted input,
because when I test the resulting N value against the expected value, they
match:


octave:10002> N
N =  50005000
octave:10003> sum([1:10000])
ans =  50005000


So, it could be that what I'm seeing is related to the freeze bug in some way.
 I guess I would describe it as a simultaneous input/output terminal problem. 
It's as though some text of the input buffer is making its way into the output
buffer prematurely, e.g.:


octave:9429> N+=9428;
octave:9430> N+=9429;
9884;
octave:9431> N+=9430;
octave:9432> N+=9431;


that hunk of text that appears always seems to be a number or portion of a
number that is ahead of the processed script line.

I think what I'm seeing isn't quite the same as what you are describing with
dropped blocks of data when pasting using "screen".

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53521>

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