bugGNU Octave - Bugs: bug #63809, Octave GUI Crashing When Opening...

 
 

bug #63809: Octave GUI Crashing When Opening on Windows 11

Submitter:  None
Submitted:  Wed 15 Feb 2023 04:40:18 PM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  Chloe Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 7.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 31 Mar 2023 12:55:05 PM UTC, comment #44: 

There is probably nothing Octave can do but wait for Avast to fix their scanner.

Closing report.

Markus Mützel <mmuetzel>
Group administrator
Tue 07 Mar 2023 10:07:47 PM UTC, comment #43: 

That indeed solved the issue.

comment #42:

> Uninstall AVAST.
>
> Dmitri.
> --
>

Anonymous
Tue 07 Mar 2023 09:51:38 PM UTC, comment #42: 

Uninstall AVAST.

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Tue 07 Mar 2023 09:33:25 PM UTC, comment #41: 

Since I yesterday performed Windows 10 update I have the very same issue, CLI works so does plotting, but GUI doesn't, throws out a white window for a moment and closes then.
Running GUI from gdb:

Browse to the folder where Octave is installed and open the shell by double-clicking the cmdshell.bat script.
At the prompt, type gdb octave. That should start gdb attached to the octave executable.
At the (gdb) prompt, type r --gui. That should start Octave in GUI mode.

gives exactly the same that was already reported

(gdb) r --gui
Starting program: C:\Octave\Octave-7.3.0\mingw64\bin\octave.exe --gui
[New Thread 7968.0x43c]
[New Thread 7968.0xd58]
[New Thread 7968.0x3e68]
C:\Octave\Octave-7.3.0\mingw64\bin\octave.exe: No error
[Thread 7968.0x3e68 exited with code 3221225477]
[Thread 7968.0x43c exited with code 3221225477]
[Thread 7968.0xd58 exited with code 3221225477]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.

Anonymous
Wed 01 Mar 2023 05:54:07 AM UTC, comment #40: 

Hi, I currently have 7.3.0 and I am having the same problems with octave I have tried uninstalling and reinstalling octave and deleting the octave-gui.ini file. Nothing has worked. I followed the instruction on Collecting gdb backtrace information and got this.

(gdb) r --gui
Starting program: C:\Program Files\GNU Octave\Octave-7.3.0\mingw64\bin\octave.exe --gui
[New Thread 21532.0x5938]
[New Thread 21532.0x43f4]
[New Thread 21532.0x2aa8]
C:\Program Files\GNU Octave\Octave-7.3.0\mingw64\bin\octave.exe: No error
[Thread 21532.0x5938 exited with code 3221225477]
[Thread 21532.0x43f4 exited with code 3221225477]
[Thread 21532.0x2aa8 exited with code 3221225477]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.

My PC Specs are:
AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx     2.30 GHz
AMD Radeon(TM) RX Vega 10 Graphics
Running Windnows 11

Charles Kirkland III <thatguycarlo>
Sat 25 Feb 2023 07:02:19 PM UTC, comment #39: 

комментарий №38:

> Thanks! What does:
>
> _opengl_info_.renderer
>
> return (at octave CLI prompt)?



octave:1> __opengl_info__.renderer
ans = llvmpipe (LLVM 12.0.1, 256 bits)


Vladimir

Vladimir <vladimir_r>
Thu 23 Feb 2023 02:35:49 PM UTC, comment #38: 

Thanks! What does:


__opengl_info__.renderer


return (at octave CLI prompt)?

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Thu 23 Feb 2023 02:30:44 PM UTC, comment #37: 

11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz   2.42 GHz
NVIDIA GeForce MX350



Thanks for taking the time to report this bug.

Without a stack trace from the crash it's very hard to determine
what caused it. Can you get us a stack trace? Please see
http://wiki.octave.org/Debugging_Octave for more information on
how to do so. Thanks in advance!

Norbert <shanghai2022>
Thu 23 Feb 2023 02:13:55 PM UTC, comment #36: 

@Norbert: What is your hardware (CPU/GPU)?

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Thu 23 Feb 2023 01:32:27 PM UTC, comment #35: 

I have exactly the same issue on Windows 10 and it happened (I believe) after two Windows updates took place but I don't have any fix for it:

February 14, 2023—KB5022834 (OS Builds 19042.2604, 19044.2604, and 19045.2604)

February 14, 2023-KB5022729 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2

CVE-2023-21808 - .NET Framework Remote Code Execution Vulnerability
This security update addresses a vulnerability in the MSDIA SDK where "an untrusted pointer dereference can cause memory corruption", leading to a crash or remove code execution. For more information please see CVE-2023-21808.

p.s.
I tried running under gdb with and without admin rights with identical errors as below I deleted the ini file reinstalled etc.. all futile no Octave GUI works in none of the 7.x versions.

(gdb) r --gui
Starting program: F:\Programme\Octave-7.1.0\mingw64\bin\octave.exe --gui
[New Thread 19260.0x48e4]
[New Thread 19260.0x4b10]
[New Thread 19260.0x462c]
F:\Programme\Octave-7.1.0\mingw64\bin\octave.exe: No error
[Thread 19260.0x48e4 exited with code 3221225477]
[Thread 19260.0x462c exited with code 3221225477]
[Thread 19260.0x4b10 exited with code 3221225477]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb)



Thanks for taking the time to report this bug.

Without a stack trace from the crash it's very hard to determine
what caused it. Can you get us a stack trace? Please see
http://wiki.octave.org/Debugging_Octave for more information on
how to do so. Thanks in advance!

Norbert <shanghai2022>
Tue 21 Feb 2023 06:12:17 PM UTC, comment #34: 


> Try to switch yours to "Windows Console Host”.


No difference running in conhost.

Vladimir <vladimir_r>
Tue 21 Feb 2023 03:54:55 PM UTC, comment #33: 
Dmitri A. Sergatskov <dasergatskov>
Tue 21 Feb 2023 03:13:40 PM UTC, comment #32: 

How is going?
I will be available to test something this evening and tomorrow if you need collect some information regarding this issue.

Vladimir <vladimir_r>
Fri 17 Feb 2023 09:58:52 PM UTC, comment #31: 

комментарий №30:

> ./octave-launch --gui  --experimental-terminal-widget
>
> (in 7.x it is mostly a useless demo, but it should be 1/2 useful
> in 8.0.90. This is just to check thatthe problem is with terminal emulator.)


For both versions window WITH UI controls appears on the screen for a moment.


Vladimir <vladimir_r>
Fri 17 Feb 2023 08:37:37 PM UTC, comment #30: 

Also:


./octave-launch --gui  --experimental-terminal-widget


(in 7.x it is mostly a useless demo, but it should be 1/2 useful
in 8.0.90. This is just to check thatthe problem is with terminal emulator.)

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Fri 17 Feb 2023 08:12:23 PM UTC, comment #29: 


комментарий №28:

> ok. so there's at least one working baseline.  if you attempt the same thing without the --no-gui, does it crash as before?


Yep

Vladimir <vladimir_r>
Fri 17 Feb 2023 08:10:59 PM UTC, comment #28: 

ok. so there's at least one working baseline.  if you attempt the same thing without the --no-gui, does it crash as before?

Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 08:01:05 PM UTC, comment #27: 


комментарий №26:

> 1) do you get the same results if you use the octave bash shell that you used to run gdb?
> - run cmdshel.bat
> - cd c:/octave/octave-7.3.0-w64
> - ./octave-launch --no-gui


Yes, it works fine. I could launch and execute some commands.

Vladimir <vladimir_r>
Fri 17 Feb 2023 04:44:48 PM UTC, comment #26: 

sorry, strange, not stage.

1) do you get the same results if you use the octave bash shell that you used to run gdb?
- run cmdshel.bat
- cd c:/octave/octave-7.3.0-w64
- ./octave-launch --no-gui


2) does anyone know if windows 10 22h2 started including the windows 11 command interpreter we've had to tell some people to disable?

Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 04:37:39 PM UTC, comment #25: 

That is stage.  In keeping with odd coincidences, I often see that same behavior (ignoring first character) when running octave-online.net in chrome on my Android device.

Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 03:50:30 PM UTC, comment #24: 


комментарий №23:

> are you able to run octave in non-gui mode?  if you don't have installed shortcuts, open a CMD prompt type
>
> cd C:\Octave\octave-7.3.0-w64
> octave-launch --no-gui
>
> and let us know what happens


It starts, but seems to be broken:

C:\Octave\octave-7.3.0-w64>octave-launch.exe --no-gui

C:\Octave\octave-7.3.0-w64>GNU Octave, version 7.3.0
Copyright (C) 1993-2022 The Octave Project Developers.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.

Octave was configured for "x86_64-w64-mingw32".

Additional information about Octave is available at https://www.octave.org.

Please contribute if you find this software useful.
For more information, visit https://www.octave.org/get-involved.html

Read https://www.octave.org/bugs.html to learn how to submit bug reports.
For information about changes from previous versions, type 'news'.

octave:1> help
'elp' is not recognized as an internal or external command,
operable program or batch file.

C:\Octave\octave-7.3.0-w64>

Vladimir <vladimir_r>
Fri 17 Feb 2023 03:42:09 PM UTC, comment #23: 

are you able to run octave in non-gui mode?  if you don't have installed shortcuts, open a CMD prompt type

cd C:\Octave\octave-7.3.0-w64
octave-launch --no-gui

and let us know what happens

Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 03:32:15 PM UTC, comment #22: 


комментарий №21:

> those messages are normal and aren't related to the current issue.
>
> can you try the gdb trace one more time from that folder?


(gdb) r --gui
Starting program: C:\Octave\octave-7.3.0-w64\mingw64\bin\octave.exe --gui
[New Thread 9640.0xf10]
[New Thread 9640.0x45ac]
[New Thread 9640.0x2f08]
C:\Octave\octave-7.3.0-w64\mingw64\bin\octave.exe: No error
[Thread 9640.0xf10 exited with code 3221225477]
[Thread 9640.0x45ac exited with code 3221225477]
[Thread 9640.0x2f08 exited with code 3221225477]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(

Vladimir <vladimir_r>
Fri 17 Feb 2023 03:31:25 PM UTC, comment #21: 

those messages are normal and aren't related to the current issue.

can you try the gdb trace one more time from that folder?

Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 03:29:14 PM UTC, comment #20: 

The same issue running from C:\Octave folder.

Also I noticed errors during post-install script like on screenshot.


Vladimir <vladimir_r>
Fri 17 Feb 2023 03:27:45 PM UTC, comment #19: 


> qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
> This application failed to start because no Qt platform plugin  could be initialized. Reinstalling the application may fix this problem.


BTW, this is similar to the mysterious crashes we get on buildbots every now and then:


Jan 30 13:19:50 amd xdg-desktop-portal-kde[406633]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Jan 30 13:19:50 amd xdg-desktop-portal-kde[406633]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

                                                    Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Jan 30 13:19:50 amd systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump.


Jan 30 13:19:51 amd systemd-coredump[406663]: [🡕] Process 406633 (xdg-desktop-por) of user 1002 dumped core.



Dmitri.
--


Dmitri A. Sergatskov <dasergatskov>
Fri 17 Feb 2023 03:16:51 PM UTC, comment #18: 

@Dmitri - thanks, rereading now I didn't notice the executable path before.

@vladimir, can you try not installing inside of your personal profile folder?  some windows security profiles are known to restrict running certain executables from within different parts of the users local profile.

I think the default is C:/Programs Files/ when installing as an administrator.  To prevent the possibility of admin permissions or pathname-with-spaces being an issue, can you try:

- create a c:\Octave folder
- use the zip package, and unzip to a octave-version subfolder.
- after unzip, run the post-install.bat file in the root of that program folder (this is done automatically by the exe installer but should be done manually by a zip user)
- try running the octave-launch.exe file

Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 03:13:21 PM UTC, comment #17: 


комментарий №13:

> >Starting program: C:\Users\user\AppData\Local\Programs\octave-7.3.0-w64\mingw64\bin\octave.exe --gui
>
>
> I wonder if installing as a user or admin system-wide makes a difference.


That was under user without admin rights. GDB running under admin user shows different error:

Reading symbols from octave...
(No debugging symbols found in octave)
(gdb) r --gui
Starting program: C:\Users\admin\Desktop\octave-7.3.0-w64\mingw64\bin\octave.exe --gui
[New Thread 15764.0x37fc]
[New Thread 15764.0x1948]
[New Thread 15764.0x3440]
C:\Users\admin\Desktop\octave-7.3.0-w64\mingw64\bin\octave.exe: No error
[Thread 15764.0x3440 exited with code 3221225477]
[Thread 15764.0x37fc exited with code 3221225477]
[Thread 15764.0x1948 exited with code 3221225477]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb)

Vladimir <vladimir_r>
Fri 17 Feb 2023 03:00:10 PM UTC, comment #16: 


комментарий №14:

> @vladimir - ok. please let us know if you're able to try 8.0.90


8.0.90 has the same issue.

Vladimir <vladimir_r>
Fri 17 Feb 2023 02:58:33 PM UTC, comment #15: 


комментарий №11:

> to be clear, your comment #10 is referring to 8.0.90? or answering how you installed 7.3.0?


No difference.
Also I turned off antivirus and extract the distributions from archives once again to be sure.
That DLLs from qt5 folder were there before.

Vladimir <vladimir_r>
Fri 17 Feb 2023 02:56:38 PM UTC, comment #14: 

@vladimir - ok. please let us know if you're able to try 8.0.90

@dmitri - the zip archives should be "installable" and usable in userspace, so that shouldn't matter.

Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 02:48:40 PM UTC, comment #13: 


>Starting program: C:\Users\user\AppData\Local\Programs\octave-7.3.0-w64\mingw64\bin\octave.exe --gui



I wonder if installing as a user or admin system-wide makes a difference.

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Fri 17 Feb 2023 02:46:58 PM UTC, comment #12: 

Everything so far concerns 7.3.0

Vladimir <vladimir_r>
Fri 17 Feb 2023 02:40:18 PM UTC, comment #11: 

to be clear, your comment #10 is referring to 8.0.90? or answering how you installed 7.3.0?

Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 02:29:12 PM UTC, comment #10: 

I tried both installer and from zip. No difference.

Vladimir <vladimir_r>
Fri 17 Feb 2023 02:27:29 PM UTC, comment #9: 

Is it possible you anti-virus software put some files in "quarantine"? In particular, "mingw64\qt5\plugins\platforms\qwindows.dll". But might also be any other file/library...

Markus Mützel <mmuetzel>
Group administrator
Fri 17 Feb 2023 02:09:39 PM UTC, comment #8: 


How did you install version 7.3.0 when not done via pacman?

can you try the current octave 8 release candidate?  it is labeled as version 8.0.90 and the different installers can be downloaded from https://alpha.gnu.org/gnu/octave/


Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 12:46:35 PM UTC, comment #7: 

(gdb) r --gui
Starting program: C:\Users\user\AppData\Local\Programs\octave-7.3.0-w64\mingw64\bin\octave.exe --gui
[New Thread 12188.0x3234]
[New Thread 12188.0x2db4]
[New Thread 12188.0x31a4]
qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

C:\Users\user\AppData\Local\Programs\octave-7.3.0-w64\mingw64\bin\octave.exe: No error
[Thread 12188.0x31a4 exited with code 3221227010]
[Thread 12188.0x3234 exited with code 3221227010]
[Thread 12188.0x2db4 exited with code 3221227010]
[Inferior 1 (process 12188) exited with code 030000003002]

Vladimir <vladimir_r>
Fri 17 Feb 2023 12:40:39 PM UTC, comment #6: 

Deleting the octave-gui.ini file has no effect.

Vladimir <vladimir_r>
Fri 17 Feb 2023 12:35:32 PM UTC, comment #5: 

did you try deleting the octave-gui.ini file mentioned in previous comments?

Would one of you be able to follow the instructions at

https://wiki.octave.org/FAQ

Under Octave does not start/ Collecting gdb backtrace information / if Octave is immediately crashing and closing

To get a gdb trace of the crash, and the man save the output to a text file and upload it here? 

Nicholas Jankowski <nrjank>
Group Member
Fri 17 Feb 2023 12:07:27 PM UTC, comment #4: 

And another one:

Faulting application name: octave-gui.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2546, time stamp: 0xe8e9ac9b
Exception code: 0xe06d7363
Fault offset: 0x000000000002cd29
Faulting process id: 0x130
Faulting application start time: 0x01d942c6ad545523
Faulting application path: C:\Users\user\AppData\Local\Programs\OCTAVE~1.0-W\mingw64\bin\octave-gui.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: f9ee385d-bf48-47d3-a9eb-9c76bcf64157
Faulting package full name:
Faulting package-relative application ID:

Vladimir <vladimir_r>
Fri 17 Feb 2023 12:05:15 PM UTC, comment #3: 

A bit more information on this issue from the Windows Event Viewer:

Faulting application name: octave-gui.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.2130, time stamp: 0xb5ced1c6
Exception code: 0xc0000005
Fault offset: 0x000000000002fcaf
Faulting process id: 0x130
Faulting application start time: 0x01d942c6ad545523
Faulting application path: C:\Users\user\AppData\Local\Programs\OCTAVE~1.0-W\mingw64\bin\octave-gui.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9ef9eacd-3af2-4f1a-9a52-4a35f3f02564
Faulting package full name:
Faulting package-relative application ID:

Vladimir <vladimir_r>
Fri 17 Feb 2023 11:49:08 AM UTC, comment #2: 

I have the same issue too.
I have tried versions 6.4.0 - 7.3.0, The same issue appears regardless the version.
But I can run the latest verson of Octave installed with pacman package manager in MSYS2 environment, for instance.

My PC config:
Windows 10 Pro 22H2 Build 19045.2604
Intel Core i7-8565U CPU
Intel UHD Graphics 620
Lenovo ThinkPad T490s

Vladimir <vladimir_r>
Wed 15 Feb 2023 05:02:51 PM UTC, comment #1: 

We've already seen a couple of reports of Octave not opening for some users. Unfortunately, we don't have steps to reproduce that error yet. So, it is difficult to fix this properly in Octave so that it won't happen again.

Most users could restore the GUI by deleting the file with GUI settings. That file is stored at the following path on Windows:
"C:\Users\USERNAME\AppData\Roaming\octave\octave-gui.ini"

Where USERNAME is your Windows user name.

Markus Mützel <mmuetzel>
Group administrator
Wed 15 Feb 2023 04:40:18 PM UTC, original submission:  

GNU Octave (GUI) keeps crashing when opening. Occasionally it starts loading the window then says (not responding) and closes. All other times it comes up with an almost blank screen for a few seconds then closes. The GNU Octave (CLI) works fine. I am on Windows 11 Octave version 7.3.0

I have tried uninstalling and reinstalling, restarting my computer, and running as an administrator multiple times.

Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files

 

Depends on the following items: None found

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 thatguycarlo (Posted a comment)
  • -email is unavailable- added by shanghai2022 (Posted a comment)
  • -email is unavailable- added by dasergatskov (Posted a comment)
  • -email is unavailable- added by nrjank (Posted a comment)
  • -email is unavailable- added by vladimir_r (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 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-03-31 mmuetzel StatusNone Invalid / Not an Octave Bug
        Open/ClosedOpen Closed
    2023-02-17 vladimir_r Attached File- Added post-install_errors.png, #54369
    2023-02-17 mmuetzel Carbon-CopyRemoved 102357 -

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code