bugGNU Octave - Bugs: bug #53953, CTRL+C is not passed to working...

 
 

bug #53953: CTRL+C is not passed to working script environment

Submitted by:  None
Submitted on:  Mon 21 May 2018 08:25:05 AM UTC  
 
Category:  Performance Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Performance
Status:  None Assigned to:  None
Originator Name:  Hale Originator Email:  -email is unavailable-
Open/Closed:  Open Release:  4.4.0
Operating System:  Microsoft Windows

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Thu 07 Jun 2018 02:05:27 AM UTC, comment #5:

Well, I am not sure, is it the same. But I upgraded from 4.2.2 to 4.4.0, so I do not know how that was in 4.3.

From my perspective, the difference is that CTRL+C has absolutely normal effect on the script itself, but it is not passed to the environment of child processes, like external solvers (Windows executables).

I am using OpenEMS solver. In the past, I was stopping it with CTRL+C from GUI console by demand, when it was going wrong way. Now I have to kill the process unsafely, which can bring undesired impact on the system.

Considering _run_test_suite_, I confirm, it is passed and can be terminated with CTRL+C during any test, and not between tests only. But with some minimal delay (about 1/3-1/2 sec).
May I guess? Can this delay be related to problems of passing event messages between processes? So in case of external computational binary, the messages are delayed infinitely?

So, probably, it can be the same problem as in the bug #53635.

Anonymous
Wed 06 Jun 2018 08:10:14 PM UTC, comment #4:

See also bug #53635. Maybe that one should be reopened and this one closed since there is more information about the problem in the discussion there.

John W. Eaton <jwe>
Project Administrator
Sat 26 May 2018 01:30:21 PM UTC, comment #3:

This bug is really impacting my job performance. Killing processes and restarting all the environment every time the calculation isn't going as expected, or worse, having almost complete calculation go to crap because windows decided, Octave is not responding is not a way things should be.

Anonymous
Tue 22 May 2018 12:33:30 AM UTC, comment #2:

P.S. sorry for weird Engrish...it's hard switching own locales in the morning.

Anonymous
Tue 22 May 2018 12:29:49 AM UTC, comment #1:

Additional comment:

Octave 4.4.0 can freeze and be terminated by system "as not responding", while binary solver is working in console.
Probably, that is the same bug of miscommunication between Octave and external tools in version 4.4.0
Previously I was using ver. 4.2.2, which did not had execution problems, rather than bugs in graphics/text formatting (which was the reason for upgrade).

Anonymous
Mon 21 May 2018 08:25:05 AM UTC, original submission:

In previous versions I could stop a script execution by pressing CTRL+C. Particularly, when running external binary solvers, like OpenEMS, CTRL+C was passed to the solver causing both, solver and the script stopping.

In version 4.4.0 pressing CTRL+C in GUI console does not have any effect on script execution. There is no way to interrupt the script any more.

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 jwe (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    No changes have been made to this item

    Back to the top


    Powered by Savane 3.3