[Octave-bug-tracker] [bug #66409] Slow startup and crashes of Octave on W10 x64

[anonyme]

Follow-up Comment #7, bug #66409 (group octave):


[comment #6 commentaire #6 :]
> I'm assuming the zip-archive approach made no difference no matter the
> location of the program? (trying outside of program files, a C:/Octave folder
> with no spaces, etc.), and temporarily disabling local security software
> makes no difference?

Indeed, no difference.
 
> Are you able to run the command line only version of octave?  Open a CMD
> prompt, cd to the root folder, and run octave-launch --no-gui (there may also
> have been a CLI shortcut created, that should do the same thing)

The main user said he can run it. No issues.
 
> if that runs fine, can you try toggling the hardware/software rendering?
> perhaps a driver update is causing a problem, which would make sense that it
> affects new and old versions.
> https://docs.octave.org/latest/Hardware-vs-Software-Rendering.html
> 
> Last, you said this is on Win 10, but can you verify that Windows Terminal is
> not installed/set as default? longshot here, as this behavior doesn't sound
> related and it should produce a warning - but can you check using the
> instructions here:
> 
> https://octave.discourse.group/t/workaround-for-weird-behavior-of-command-window-widget-in-windows/4981

Tested to switch the  HW/SW rendering on a test VM. Issues still there.

But the main user said that he's experiencing no issues when he toggled off
the files explorer widget. It's probably what causes all theses issues when
the Octave is fully launched.
At the moment, he's running Octave without it and workds with commands. But he
really need this widget.

Regards,


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
Message posté via Savannah
https://savannah.gnu.org/

signature.asc
Description: PGP signature