bugGNU Octave - Bugs: bug #64846, Octave 8.3.0 GUI crashes while...

 
 

bug #64846: Octave 8.3.0 GUI crashes while processing with new Windows Terminal

Submitter:  None
Submitted:  Thu 02 Nov 2023 10:06:18 PM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Duplicate Assigned to:  None
Originator Name:  Luiz Meleiro Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 8.3.0
Operating System:  * Microsoft Windows Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 10 Nov 2023 10:08:59 AM UTC, comment #8: 

Closing as duplicate of bug #62791.

Markus Mützel <mmuetzel>
Group administrator
Wed 08 Nov 2023 04:44:22 PM UTC, comment #7: 

Thanks for confirming. I know we had run into a number of issues with the new Terminal before but this is the first i heard it was specifically tied to an event (running a script, or perhaps attempting to display the output?)

It seems that the workaround works for you for now. We have a few other reports around this general Windows Terminal topic, but this seems slightly different. Still close as duplicate or fixed? leaving open for now

Nicholas Jankowski <nrjank>
Group Member
Wed 08 Nov 2023 04:16:00 PM UTC, comment #6: 


comment #5:

> I was having the same issue here. After executing a script in the GUI (and some times in the middle of the processing), it wouldn't return to the state where it expects for new input (by showing the input arrows ">>"). The input cursor kept blinking and the task manager showed intense use of processor but I couldn't type any entries nor I could stop the script by pressing ctrl + c.
>
> In my case, the CLI was opening with the execution of the GUI and I was using Windows 11.
>
> The problem stopped after changing the default terminal on windows to "Windows Console Host".


Thank you very much, it seems changing the default terminal to "Windows Console Host" has solved the problem (so far).

Mohammed Elmusrati <elmusrati>
Wed 08 Nov 2023 03:58:31 PM UTC, comment #5: 

I was having the same issue here. After executing a script in the GUI (and some times in the middle of the processing), it wouldn't return to the state where it expects for new input (by showing the input arrows ">>"). The input cursor kept blinking and the task manager showed intense use of processor but I couldn't type any entries nor I could stop the script by pressing ctrl + c.

In my case, the CLI was opening with the execution of the GUI and I was using Windows 11.

The problem stopped after changing the default terminal on windows to "Windows Console Host".

Anonymous
Tue 07 Nov 2023 04:02:54 PM UTC, comment #4: 

Could be another instance of the Windows Terminal issue.
For a potential work-around:
https://octave.discourse.group/t/cli-is-open-together-with-gui-in-octave-7-1-on-windows-11/2753/6

Markus Mützel <mmuetzel>
Group administrator
Tue 07 Nov 2023 03:04:41 PM UTC, comment #3: 

so, just to confirm - you recently noticed the change while using 8.3.0, but even going back to older version the same problem happens? What operating system are you running, and have you made any recent system changes?

Nicholas Jankowski <nrjank>
Group Member
Tue 07 Nov 2023 01:53:34 PM UTC, comment #2: 


comment #1:

> Can you please be more specific about what action results in a crash? What do you mean by “try to run any program”? Does it crash when loading? When doing something at the command line? When opening something in the editor?


I've encountered a sudden issue when using the GUI version of Octave 8.3. Initially, it opens as expected, but when I attempt to run a simple code, it occasionally becomes unresponsive and hangs. Even if it runs smoothly on the first attempt, there's a higher likelihood of it hanging on subsequent trials, rendering it unresponsive. I rely on Octave for teaching in my course, so I've experimented with installing older Octave versions, but the problem persists. Interestingly, the command-line interface (CLI) version works flawlessly. Nevertheless, the GUI is more convenient and user-friendly. It's worth noting that I'm using a computer with an AMD R-7 series processor, and I wonder if this might be the cause, as Octave functions perfectly on my other computer with an Intel-based processor.

Mohammed Elmusrati <elmusrati>
Thu 02 Nov 2023 11:24:27 PM UTC, comment #1: 

Can you please be more specific about what action results in a crash? What do you mean by “try to run any program”? Does it crash when loading? When doing something at the command line? When opening something in the editor?

Nicholas Jankowski <nrjank>
Group Member
Thu 02 Nov 2023 10:06:18 PM UTC, original submission:  

Octave GUI, version 8.3.0, crashes when I try to run any program.

Anonymous

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Digest:
   bug dependencies.

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by elmusrati (Posted a comment)
  • -email is unavailable- added by nrjank (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 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-11-10 mmuetzel StatusConfirmed Duplicate
        Open/ClosedOpen Closed
        Dependencies- Depends on bugs #62791
    2023-11-08 nrjank Item GroupNone Segfault, Bus Error, etc.
        StatusNeed Info Confirmed
        SummaryOctave GUI, version 8.3.0, crashes Octave 8.3.0 GUI crashes while processing with new Windows Terminal
    2023-11-02 nrjank StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code