[Octave-bug-tracker] [bug #63971] Invoking Octave's Java subsystem crashes Octave

[Philip Nienhuis]

Update of bug #63971 (group octave):

                  Status:               Need Info => Invalid / Not an Octave
Bug
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #22:

Thanks for reporting back your solution :-)

Rather than feeling "I've wasted my time" (I don't) I am glad you got it
solved. And a nice thing is that you've handed us another trick to try if
Octave on Windows users report hard-to-track-down issues here - thank you for
that!

That said, it's kind of weird that you need to set Windows 7 compatibility for
Octave. I still can' t help to suspect this is related to e.g., security
policies silently set by your IT department.
On my (virtual) Windows 10 machine at work (semi-gov, so locked down quite a
bit) I'm running bleeding edge dev Octave versions all the time. I never had
to set compatibility options for any SW I use - and we have a quite a mix of
brand new, up to some really old SW running.

Closing this report with "Invalid / not an Octave bug" as there's no other
matching criterion :-)


    _______________________________________________________

Reply to this item at:

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

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