Mon 21 Mar 2016 05:28:31 PM UTC, comment #10:
Just found it, bug #45458. I'm closing this bug as a duplicate. If it turns out to not be the same problem and there are other reasons for slow initial plotting, another bug should be filed.
|
Mon 21 Mar 2016 05:27:01 PM UTC, comment #9:
Ok, so this is the known slow initial startup problem on Windows systems.
John D, is there another open bug about this already? Have we been able to confirm that it is fontconfig initialization that is contributing all of the delay on the first plot?
|
Mon 21 Mar 2016 05:21:18 PM UTC, comment #8:
I can't plot from Octave 4.0.0 in Ubuntu 14.04LTS, which I've just updated, The plot windows are created, but scrambled. Works fine on my Windows7 machine.
|
Sat 19 Mar 2016 06:29:45 PM UTC, comment #7:
Font cache, not fotcache.
|
Sat 19 Mar 2016 04:08:54 PM UTC, comment #6:
Ok, now with 4.0.1 I can plot again, and I probably could with 4.0.0, but I didn't have the patience to wait several minutes for the first plot to appear.
The first plot took several minutes to generate, but once that is done, it is working normally. It probably has to do with the fotcache that John Donoghue suggested.
Thanks for the help!
|
Sat 19 Mar 2016 03:21:09 PM UTC, comment #5:
Thanks for the suggestions. I'll try with 4.0.1 and see if I have more luck then.
By crashing, I mean that it appears to do nothing and if I try to close the blank fltk plot window, it does not respond and I'm forced to restart the program.
I have tried very basic stuff like plot([1]).
|
Sat 19 Mar 2016 02:56:44 AM UTC, comment #4:
Stupid phone.
Streams not steaks.
Caches not cashed.
Windows 10.
Character input not caramelized input.
|
Sat 19 Mar 2016 02:55:29 AM UTC, comment #3:
Flush steaks and cashed after input output on Wendy's 10. May need more testing on caramelized input.
|
Sat 19 Mar 2016 12:21:10 AM UTC, comment #2:
4.0.1-rc4 (compiled for 64-bit Windows) works fine for me on Win 10, including plotting with qt, fltk and gnuplot toolkits.
Same for the development version (4.1.0+)
I haven't used Octave a lot in Win 10 but in general I find that Octave seems to work fine in that OS.
|
Fri 18 Mar 2016 11:24:10 PM UTC, comment #1:
Thanks for the report.
By crashing, it comes up with a messaging saying it has crashed octave, or just it doesnt appear to be doing anything?
Even something as basic as plot([1]) fails?
It may be generating a fotcache the first time and take a while.
It may also be worth trying the release candidate of 4.0.1 to see if it behaves any better [1]
[1] ftp://alpha.gnu.org/gnu/octave/octave-4.0.1-rc4-installer.exe
|
Fri 18 Mar 2016 10:59:26 PM UTC, original submission:
I have a fresh install of Octave 4.0.0 on Windows 10. If I try to plot anything, Octave crashes. It does not matter if I use gnuplot or fltk. (fltk shows an empty plot window, gnuplot does not show up at all.)
|