bugGNU Octave - Bugs: bug #50045, page_output_immediately: quitting...

 
 

bug #50045: page_output_immediately: quitting for large outputs results in infinite loop

Submitter:  None
Submitted:  Fri 13 Jan 2017 10:14:43 AM UTC
   
 
Category:  Octave Function Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Other
Status:  Works For Me Assigned to:  None
Originator Name:  MT Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * dev
Operating System:  * GNU/Linux Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 21 Jan 2017 11:15:48 PM UTC, comment #7: 

Since Octave devs can't reproduce I'm going to have to close this bug.  If a new way to generate the problem arises we can test that.

Rik <rik5>
Group administrator
Sun 15 Jan 2017 01:34:27 AM UTC, comment #6: 

I'm using Kubuntu 15.10 per


lsb_release -a


octave-4.0.0 works for me.

Rik <rik5>
Group administrator
Sat 14 Jan 2017 11:01:09 PM UTC, comment #5: 

Hmm. That's weird. I was using Octave 4.0.0 in Ubuntu 16.04. Has anyone else tried to run the code in Ubuntu? I encountered this problem at first when analyzing an Octave script in terminal, but the problem is present also in the GUI. When pressing the q, it prints a huge number of "warning: broken pipe" lines. To be honest, I'm not sure whether it is an infinite loop or not, but when it consumes more than 2 GB of free memory, I have to terminate the process.

Michal Trachta <majklt>
Sat 14 Jan 2017 07:41:59 PM UTC, comment #4: 

I also see the "warning: broken pipe" message with 6000 lines of output, but no looping or memory explosion.

Mike Miller <mtmiller>
Group Member
Fri 13 Jan 2017 04:54:35 PM UTC, comment #3: 

Partial confirmation.  Using the development branch and cset 23035:60cf700e04ef, I get a warning when using the example code and the value 6000.


warning: broken pipe
warning: connection to external pager lost (pid = 2903)
warning: flushing pending output (please wait)


However, there is no infinite loop, I'm just returned to the prompt as expected.  I get similar behavior when testing with version 4.0.0 (no infinite loop).  I went back as far as version 3.6.4 and I always get a warning about a broken pipe, but everything still works correctly.

Rik <rik5>
Group administrator
Fri 13 Jan 2017 03:40:01 PM UTC, comment #2: 

Running it in GUI or in a terminal window makes no difference. The problem is present in both.

Michal Trachta <majklt>
Fri 13 Jan 2017 02:25:07 PM UTC, comment #1: 

Are you running the Octave GUI or using the command-line version of Octave in a terminal window?

John W. Eaton <jwe>
Group administrator
Fri 13 Jan 2017 10:14:43 AM UTC, original submission:  

Running a code

page_output_immediately(true)
disp(rand(5000,1)); % 5000 is OK

produces 5000 lines on screen. When I don't want to read them all I use q (quit) to skip the remaining lines and everything is fine.

When running the same code with longer output (6000 lines) and using the q option, I end up in an infinite loop printing "warning: broken pipe" on my screen. It's pretty annoying, since it consumes whole RAM quickly, so I have to kill the Octave process fast or the system becomes unresponsive.

page_output_immediately(true)
disp(rand(6000,1)); % 6000 is NOT OK

The problem is probably related to how Octave communicate with more/less in Linux.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by majklt (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-01-21 rik5 Open/ClosedOpen Closed
    2017-01-14 mtmiller StatusNone Works For Me
    2017-01-13 rik5 Release4.0.0 dev

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code