[Octave-bug-tracker] [bug #63459] Crash while Reorganizing Windows

[anonymous]

URL:
  <https://savannah.gnu.org/bugs/?63459>

                 Summary: Crash while Reorganizing Windows
                 Project: GNU Octave
               Submitter: None
               Submitted: Fri 02 Dec 2022 05:14:01 PM UTC
                Category: Performance
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Performance
                  Status: None
             Assigned to: None
         Originator Name: Mitchell Sommer
        Originator Email: mitchell.sommer7@gmail.com
             Open/Closed: Open
                 Release: 7.3.0
         Discussion Lock: Any
        Operating System: Microsoft Windows
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Fri 02 Dec 2022 05:14:01 PM UTC By: Anonymous
I just downloaded and installed Octave on my computer. I have a Dell Precision
5530 laptop, and I run Windows 11 Pro.

When I open Octave and begin reorganizing the windows, it just crashes on me.
For example, when I move the Workspace over to the very right side, Octave
crashes. When I move the Command History window down to be below the Command
Window, Octave crashes. In both of these instances, when I reopen Octave
afterward, the changes are not saved (the windows are back in their original
positions). 

However, there are some instances where it dos not crash, like if I move the
Command History window to merge with the Workspace window on the left half of
the screen (where they are originally located), they work fine, and Octave
does not crash. After this, if I close and reopen Octave, the windows remain
where I moved them.

So overall, it looks like Octave is okay with certain window movements and
merges but not with others.

I have tried restarting my computer and checking for updates through Support
Assist. Nothing has fixed the issue so far, so it may be a bug.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63459>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/