Thu 14 Apr 2016 03:55:14 PM UTC, comment #12:
I think you're probably right. Mac OSX 10.9 was released in 10/13 which makes it 2.5 years old. We support some very old releases like Ubuntu 12.04, but we're also a very small team and I think we would just recommend that user's upgrade their OS.
|
Thu 14 Apr 2016 06:36:53 AM UTC, comment #11:
Rik, comment #2 noted that this works with OSX 10.9.
My guess is that the issues with 10.7 and 10.8 are still present but not longer important.
I'm tentatively marking it as "Won't fix", but will leave it to someone more authoritative to close it.
|
Sat 21 Nov 2015 05:13:08 AM UTC, comment #10:
This bug is 2 years old. Is it still present? It seems that more people have been able to get Octave to run on OSX lately.
|
Tue 19 Nov 2013 09:22:24 PM UTC, comment #9:
No, an editor without syntax highlighting seems equally pointless to me.
If I don't get back to you about this bug within a couple of days, then we'll just release a broken GUI, I guess.
|
Tue 19 Nov 2013 07:46:56 PM UTC, comment #8:
Jordi, there is a workaround for this
issue which is downgrading qscintilla to 2.4.
with that octave-gui will not crash.
do you think this is enough to consider this bug as non-blocking
and proceed asynchronously with the release?
|
Tue 19 Nov 2013 07:39:24 PM UTC, comment #7:
I disagree.
I don't think there's a point in releasing without a working GUI on Windows and Mac OS X.
We should make this a blocking bug.
I'm working on this.
|
Mon 18 Nov 2013 08:48:25 PM UTC, comment #6:
I agree to make it not blocking. To be honest, I have no idea what might cause the crash and I don't have a OSX-System available for testing. Sending test patches to Carlo is time consuming and not very effective.
|
Mon 18 Nov 2013 07:21:42 PM UTC, comment #5:
I'm not working on this anymore as I expect most
OSX users who are currently using OSX 10.8 to upgrade
to 10.9 eventually, so it's probably not worth the effort.
On the other hand the GUI can not be considered to be usable
on OSX 10.9 either due to bug #40545.
|
Mon 18 Nov 2013 06:07:58 PM UTC, comment #4:
I prefer to make it NOT blocking and note the issue.
|
Mon 18 Nov 2013 05:54:18 PM UTC, comment #3:
This bug is listed as a blocker for the 3.8 release, but I'm not sure any further progress is being made. Do you still want to work on this right now, or should we postpone it and put a note in the README.MacOS file that versions 10.7 and 10.8 are known not to work with the GUI?
|
Mon 11 Nov 2013 10:33:23 AM UTC, comment #2:
I upgraded yesterday to Mavericks (OSX 10.9) and the editor crash does not occur anymore, so it appears this problem only affects OSX 10.8 and OSX 10.7.
|
Thu 07 Nov 2013 07:33:24 AM UTC, comment #1:
Here some mor informations:
The crash happens with QSintilla versions 2.6 or higher.
Attached a patch that strips most of the configurations of edit_area (the qscintilla editor). The remaining steps when loading an existing file related to _edit_area are:
+verbatim
_edit_area = new QsciScintilla; // in constructor
_edit_area->setText (in.readAll ()); // in load_file
QsciLexer *lexer = _edit_area->lexer (); // in update_lexer
delete lexer;
lexer = 0;
//... determine lexer from file extension
_edit_area->setLexer (lexer); // ---> crash
-verbatim-
A minimal example with those steps does not crash.
(file #29555)
|
Wed 06 Nov 2013 09:23:10 PM UTC, original submission:
a reproducible crash occurs in OSX in GUI mode.
to get the crash:
the crash happens in qscintilla::setLexer, therefore
disabling syntax highlighting in the sources is a workaround.
|