[Octave-bug-tracker] [bug #55940] pause() takes too long if you call it a bunch

[Andrew Janke]

Follow-up Comment #4, bug #55940 (project octave):

I can't reproduce this on Linux or Windows, even in VMs on the original
machine where this first appeared.

I can reproduce it on other Mac machines. The first one where I saw it was
angharad, a 5K iMac running Mojave. Here's behavior on toast, my 13" MacBook
Pro, under 5.1.0, while the machine is lightly loaded.


octave:1> for i = 1:200; t0 = tic; pause (0.2); fprintf ("%.3f  ", toc(t0));
endfor
9.602  0.358  0.722  0.201  0.629  0.201  0.209  0.210  0.204  0.204  20.079 
0.357  0.526  0.201  4.780  4.353  5.048  0.260  0.280  1.026  1.370  2.339 
2.005  0.336  6.454  2.532  3.683  2.337  3.339  5.218  1.194  1.346  3.822 
1.101  5.375  0.916  3.054  1.139  6.354  6.535  1.158  1.137  2.424  1.440 
5.022  5.926  2.021  9.747  2.177  11.538  6.867  4.241  15.702  17.544  4.638
 2.037  4.483  0.443  0.202  0.202  0.203  0.202  0.594  0.200  2.834  8.706 
6.874  1.077  10.200  12.957  11.588  3.485  3.597  12.418  1.380  10.200 
20.971  1.552  1.693  5.222  12.353  10.511  18.575  14.750  14.891  ^C
octave:1> for i = 1:200; t0 = tic; javaMethod("sleep", "java.lang.Thread",
200); fprintf ("%.3f  ", toc(t0)); endfor
10.556  3.444  1.077  0.201  0.234  3.931  0.943  5.128  4.294  0.656  3.448 
6.198  3.912  1.321  4.741  0.204  10.201  4.284  1.626  10.201  8.528  0.201 
10.201  0.815  0.201  0.209  0.200  0.200  0.205  0.328  0.204  0.206  0.204 
0.206  0.202  10.201  10.201  10.201  10.201  10.201  3.039  3.000  0.201 
0.201  0.201  0.523  2.135  0.335  0.200  0.201  0.359  0.201  0.771  0.200 
0.200  1.785  0.495  1.104  0.316  0.832  0.201  0.934  0.909  0.402  1.324 
0.289  1.939  2.635  0.982  0.201  0.958  1.583  1.020  0.201  2.138  0.201 
0.947  1.392  1.185  0.489  0.825  0.201  1.450  1.117  10.201  8.015


Happens for me in 4.4.1, 5.1.0, and default. Again, on this machine, it only
happens in the CLI, not the GUI of the same Octave, even if run at the same
time as a CLI octave process is exhibiting this behavior.

One thing I noticed is that it takes a while for Octave to respond to Ctrl-C
inputs when this is happening. So it seems like one of the individual sleep
intervals or graphics-handling steps in octave::sleep() is taking a while. And
the fact that java.lang.Thread.sleep is also taking a long time suggests that
it's not octave::sleep's code that's doing anything weird; it's something
about the overall process or machine state that's causing regular sleeps to
take a long time.

    _______________________________________________________

Reply to this item at:

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

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