Sun 03 Jul 2016 07:14:22 AM UTC, comment #14:
In my crashes, Octave did not hang.
It crashed to desktop, simply gone...
|
Sat 02 Jul 2016 08:14:26 PM UTC, comment #13:
I tied it 5 times on Win-10 with octave-4.1.0+, that went well (but slow).
But Octave-4.0.1 hung the very first run of bug.m before any line was drawn.
|
Sat 02 Jul 2016 07:55:28 PM UTC, comment #12:
@Philip, comment #11
When I submitted the file I could not run it 4 times in a row without a crash (4.0.0).
It didn't crash right away every time, sometimes I could run bug.m without a crash; sometimes even 2 or 3 times in a row.
I tried it this evening and ran it 20 times without a glitch.
|
Sat 02 Jul 2016 07:47:17 PM UTC, comment #11:
Right, remarkable that you get no crash/hang with octave-4.0.1.
Whatever, octave-4.1.0+ (future 4.2.0) runs it fine.
|
Sat 02 Jul 2016 06:39:08 PM UTC, comment #10:
@Philip, comment #9
Yes, it was me who submitted this file
|
Sat 02 Jul 2016 06:32:32 PM UTC, comment #9:
@Steven comment #7:
Did you try to run bug.m from comment #2?
|
Sat 02 Jul 2016 06:27:12 PM UTC, comment #8:
bug.m (comment #2) works fine with dev version on Windows 10.
Octave-4.0.1 gets into a solid hang when I try to run bug.m.
(FTR, I see little performance or stability differences between Windows 10 and Windows 7. From what I can see Win10 is not worse or better than Win7.
Closing report with "fixed"
|
Sat 02 Jul 2016 05:55:21 PM UTC, comment #7:
The test I've done with Octave 4.0.1 on W10 went ok.
No crashes since going from 4.0.0 to 4.0.1
|
Sat 02 Jul 2016 05:50:04 PM UTC, comment #6:
In a few moments I can try on Windows 10. Hang on...
|
Sat 02 Jul 2016 04:24:10 PM UTC, comment #5:
Do we need to wait for confirmation that the dev branch works on Windows 10, or is the fact that the problem has been resolved on Windows 7 enough indication?
|
Wed 29 Jun 2016 05:16:36 AM UTC, comment #4:
Using the script from comment #2, Octave 4.0.2 fails on the
plot, with many error messages (without crash).
On dev branch (changset d31e0f704d0b) with Win-7. it does not fail.
I did not try this on Windows-10 yet.
|
Sun 21 Feb 2016 10:56:37 PM UTC, comment #3:
The posted example repeatably works for me on Debian. Can anyone reproduce the crash on Windows with the given script?
|
Sun 24 Jan 2016 03:07:44 PM UTC, comment #2:
I have the same problem, on 2 different Windows 10 machines.
When I use Visual Studio as debugger I get:
Unhandled exception at 0x6FEB1F62 (libstdc++-6.dll) in octave-gui.exe: 0xC0000005: Access violation reading location 0x17D2B088.
or:
Unhandled exception at 0x6B3F5A41 (liboctinterp-3.dll) in octave-gui.exe: 0xC0000005: Access violation reading location 0x152AE368.
I attache bug.m, which I was not able to run more than 4 times in a row without Octave crashing.
I hope this helps!
(file #36155)
|
Sat 16 Jan 2016 07:42:50 AM UTC, comment #1:
Thanks for filing a bug report, Apostol. Can you provide a reproducible example that causes the crash?
|
Thu 19 Nov 2015 03:43:25 PM UTC, original submission:
Octave 4.0.0 (GUI) crashes when I use 2-3 times a simple plot(x,y) command. This happens on all versions of MS Windows (XP, 7, 10). It does not happen when I use the 3.8.2 GUI version.
|