bugGNU Octave - Bugs: bug #59683, octave GUI crashes permanently...

 
 

bug #59683: octave GUI crashes permanently (maybe because of catch+fix)

Submitted by:  Arian Atri <arianatri>
Submitted on:  Mon 14 Dec 2020 08:24:54 PM UTC  
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Other
Status:  Need Info Assigned to:  None
Originator Name:  Arian Atri Open/Closed:  Open
Release:  6.1.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.

 

( Jump to the original submission)

Tue 12 Jan 2021 07:37:13 AM UTC, comment #13: 

Could you please try and generate a backtrace from the crash?
For this:

  • Open Octave.
  • Execute `__debug_octave__`. This will open a new window with `gdb` attached to Octave (Octave will look irresponsive).
  • At the "(gdb)" prompt, continue Octave by executing `c`.
  • In Octave, do the steps that lead to the crash. When that crash happened, Octave will look irresponsive again.
  • At that point, return to the gdb window and execute `thread apply all bt`. This will probably output a lot of lines.
  • Copy all text from the gdb window to a text file and attach that file to this report.
Markus Mützel <mmuetzel>
Project Member
Mon 21 Dec 2020 08:07:36 PM UTC, comment #12: 

comment #11:

> Does Octave crash with every file you want to open or just with the one attached in a previous post? Is the file located on a normal hard disk or some cloud or network location?


-with every file
-normal hard disk

Arian Atri <arianatri>
Mon 21 Dec 2020 08:05:32 PM UTC, comment #11: 

Does Octave crash with every file you want to open or just with the one attached in a previous post? Is the file located on a normal hard disk or some cloud or network location?

Torsten Lilge <ttl>
Project Member
Mon 21 Dec 2020 07:53:57 PM UTC, comment #10: 

comment #9:

> My comment #6 was about another bug report and is not related to this bug report (please refer to comment #6).
>
> Let me try to summarize what your video is showing:
>
> 0 You can start octave but the initial message is partly hidden and seems to be flickering during resize
> 0 When you try to start octave by double clicking an m-file octave (silently) crashes
> 0 After that crash, octave won't start even when directly launched
> 0 After deleting the ini-file, you are again able to directly launch octave (with partly hidden start up messsage)
>
> Is this correct? Sorry, but I do not get the rest of the video where you are opening the m-file in an external editor and select some of the code.


Not only initial message is cropped but if I typed in some command like "pkg" the result message would have been cropped
After deleting the ini-file, I finally could open octave
I opened the m-file in notepad++ so I could show you that it was a normal file with lines of octave code.

Arian Atri <arianatri>
Mon 21 Dec 2020 07:36:16 PM UTC, comment #9: 

My comment #6 was about another bug report and is not related to this bug report (please refer to comment #6).

Let me try to summarize what your video is showing:

  1. You can start octave but the initial message is partly hidden and seems to be flickering during resize
  2. When you try to start octave by double clicking an m-file octave (silently) crashes
  3. After that crash, octave won't start even when directly launched
  4. After deleting the ini-file, you are again able to directly launch octave (with partly hidden start up messsage)

Is this correct? Sorry, but I do not get the rest of the video where you are opening the m-file in an external editor and select some of the code.

Torsten Lilge <ttl>
Project Member
Mon 21 Dec 2020 12:36:31 PM UTC, comment #8: 

comment #6:

> I have pushed cset http://hg.savannah.gnu.org/hgweb/octave/rev/0fc400f15e35 which prevents that the gui is launched when "--eval CODE" or a FILE is given as command line argument unless "--persist" is given, too.
>
> However, the argument check in main.cc analyzes all given arguments regardless there position in the command string. Arguments behind a possible FILE argument are obviously ignored by octave but are used to set several flags in main.in.cc. This does not only affect the test for launching the gui or not but also the already existing tests.


I captured a screen record and uploaded it on this link :
https://youtu.be/Q3BZBeYktQI
Accidentally I found another bug in the command window (GUI)!wihch is in the video.

Arian Atri <arianatri>
Fri 18 Dec 2020 06:15:25 AM UTC, comment #7: 

Please ignore my comment #6. It is intended for bug #59628.

Torsten Lilge <ttl>
Project Member
Thu 17 Dec 2020 09:02:50 PM UTC, comment #6: 

I have pushed cset http://hg.savannah.gnu.org/hgweb/octave/rev/0fc400f15e35 which prevents that the gui is launched when "--eval CODE" or a FILE is given as command line argument unless "--persist" is given, too.

However, the argument check in main.cc analyzes all given arguments regardless there position in the command string. Arguments behind a possible FILE argument are obviously ignored by octave but are used to set several flags in main.in.cc. This does not only affect the test for launching the gui or not but also the already existing tests.

Torsten Lilge <ttl>
Project Member
Wed 16 Dec 2020 07:23:01 PM UTC, comment #5: 

I have already seen negative coordinates in my own ini file. From what i have observed so far, this is related to tabbed widgets and never resulted in crashes or unexpected behavior.

Torsten Lilge <ttl>
Project Member
Wed 16 Dec 2020 06:30:09 PM UTC, comment #4: 

Thank you for providing the ini-file. With this ini file, octave starts without problems on Linux and Windows 7 for me. Consequently, I think the issues you are seeing are not related to a possibly messed up ini file.

I am not sure if I understand your comment #2 correctly. So, if octave starts normally after you have deleted the ini file, it still crashes each time when

- you open an editor file
- you plot a huger figure (what is huge?)

or even sometimes in the middle of a command execution without any further indication?

Torsten Lilge <ttl>
Project Member
Wed 16 Dec 2020 06:13:16 PM UTC, comment #3: 

It doesn't crash for me if I replace my octave-gui.ini with the one you uploaded.
I notice that some of the widgets have negative coordinates. (I'm not sure what that means. Maybe related to monitor layout?)
Might be related to that or something different.

CC'ing Torsten. He is probably more able to read that file than I am.

Markus Mützel <mmuetzel>
Project Member
Wed 16 Dec 2020 05:59:17 PM UTC, comment #2: 

comment #1:

> There is nothing in that file that looks suspicious.
> Can you reproduce the issue now that Octave work correctly for you?
>

     ok I did try to reproduce that error now whenever I open .m files it crashes
also if anything happens inside the octave GUI that causes it to close/crash(things like showing a huge figure or even closing the app in the middle of the process) will make the octave GUI un-openable.
(I uploaded octave_gui.ini file (%APPDATA%/octave) for you)

(file #50491)

Arian Atri <arianatri>
Wed 16 Dec 2020 03:50:10 PM UTC, comment #1: 

There is nothing in that file that looks suspicious.
Can you reproduce the issue now that Octave work correctly for you?

Markus Mützel <mmuetzel>
Project Member
Mon 14 Dec 2020 08:24:54 PM UTC, original submission:  

▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐what happned▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐
I was loading a really simple project(file is attached) and it failed to load and crashed, then I opened that file again(directly by clicking on it) and it again crashed.
I opened octave GUI by clicking on its icon, which also crashed!!
notice that until now I was only using GUI version and octave CLI is working fine.
uninstalling and reinstalling it was sometimes successful and it could run fine(sometimes) until I opened that faulty file and the process repeated GUI crashes etc...
so I guess it has something to do with the catch of octave GUI (maybe it opens the recent file on startup)
▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐fix▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐▐
by removing everything on this path(%APPDATA%/octave) octave GUI will run without problems so... I guess kinda solved it IDK.

Arian Atri <arianatri>

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #50491:  octave-gui.ini added by arianatri (23KiB - application/octet-stream)
file #50460:  color_tamrin.m added by arianatri (1KiB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by ttl (Posted a comment)
  • -email is unavailable- added by mmuetzel
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by arianatri (Submitted the item)
  • -email is unavailable- added by arianatri
  •  

    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.

     

     

     

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-12-20 ttl StatusReady For Test => Need Info
    2020-12-17 ttl StatusNeed Info => Ready For Test
    2020-12-16 mmuetzel Carbon-Copy- => Added ttl
    2020-12-16 arianatri Attached File- => Added octave-gui.ini, #50491
    2020-12-16 mmuetzel StatusNone => Need Info
    2020-12-14 arianatri Attached File- => Added color_tamrin.m, #50460
        Carbon-Copy- => Added atriarian118@gmail.com

    Back to the top


    Powered by Savane 3.5