|
From: | anonymous |
Subject: | [Octave-bug-tracker] [bug #52839] Octave GUI Crash on Snap ocor Startup |
Date: | Mon, 8 Jan 2018 15:12:46 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063 |
URL: <http://savannah.gnu.org/bugs/?52839> Summary: Octave GUI Crash on Snap ocor Startup Project: GNU Octave Submitted by: None Submitted on: Mon 08 Jan 2018 08:12:45 PM UTC Category: GUI Severity: 3 - Normal Priority: 5 - Normal Item Group: Unexpected Error Status: None Assigned to: None Originator Name: speedcoder Originator Email: Open/Closed: Open Discussion Lock: Any Release: 4.2.1 Operating System: Microsoft Windows _______________________________________________________ Details: Octave 4.2.1 on my Windows 10 system crashes when I [snap]( https://www.techrepublic.com/article/snap-a-truly-slick-feature-in-windows-10) its window to the right side of the second monitor which is on the right of the main monitor. Snapping to the left side on the main monitor works fine. It crashes with the following error: Unhandled exception at 0x00007FFDF097775F (ntdll.dll) in octave-gui.exe: 0xC0000374: A heap has been corrupted (parameters: 0x00007FFDF09D86B0). Once, snapping the window to the right worked. I then exited Octave GUI when paused in debugging. After that I could not reopen Octave GUI without it crashing. I was able to work around it and get Octave GUI running again on my system by deleting two of Octave's temp files (username was my user name): C:\Users\username\.config\octave\qt-settings C:\Users\username\.config\4.2.1\qsci\octave_kbf.pap. This issue is similar to bug #41953: GUI Crash on Startup. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?52839> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |