bugGNU Octave - Bugs: bug #63849, Crash when plotting dotted line...


bug #63849: Crash when plotting dotted line using system OpenGL

Submitter:  Philip Nienhuis <philipnienhuis>
Submitted:  Tue 28 Feb 2023 03:07:50 PM UTC
Category:  Plotting with OpenGL Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  None Assigned to:  None
Originator Name:  Philip Nienhuis Open/Closed:  * Open
Release:  * 8.0.90 Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup

Jump to the original submission

Wed 08 Mar 2023 09:45:42 PM UTC, comment #6: 

AFAIU my bug report is about OpenGL incompatibilities, I'm not sure if it is related to threading issues as well (but could be, I just don't know).
As expected, using fltk doesn't make much difference for this bug report.

Philip Nienhuis <philipnienhuis>
Group Member
Tue 07 Mar 2023 11:27:34 PM UTC, comment #5: 

Running cli and fltk graphics should avoid threading issues, should not it? At least TSAN-compiled octave does not complain when I do misc plots. Yet, plot(1:10); print("t1.svg") hangs
for me on windows 11 (i9-9880 CPU / integrated intel 630 graphics), though I do get a few "GLPS warning: Unknown token in buffer" before that.


Dmitri A. Sergatskov <dasergatskov>
Wed 01 Mar 2023 07:27:24 AM UTC, comment #4: 

Like I wrote somewhere else, we are unfortunately in a situation where Octave can crash with the software or with the hardware OpenGL drivers. That seems to depend on the system on which Octave is executed.
The actual reason might be some timing issues between different threads. It might be that it just so happens on some systems that the relevant functions are executing in a "good" order and on other systems in a "bad" order with either the software or the hardware OpenGL renderers.
For the time being, the best we can do imho is to advice affected users to test if updating their graphics drivers makes a difference. (The timing might just be so different that the relevant functions happen to execute in a "good" order.) Or if that doesn't work switch from hardware to software renderer (or vice versa).

Since both renderers could lead to Octave crashing on some systems and the hardware renderers are orders of magnitude faster (if they are working), I'd vote for keeping the hardware renderer the default in the installer.

Markus Mützel <mmuetzel>
Group Member
Tue 28 Feb 2023 07:07:49 PM UTC, comment #3: 

Octave-7.3.0 also crashes if I disable the software OpenGL driver (I hadn't checked that yet).

IIRC (please correct me if I'm wrong) a while ago the system OpenGL became the default for mxe-octave; is this still advisable, if such basic commands make Octave crash? Radeon quite isn't a rare graphics platform.

Philip Nienhuis <philipnienhuis>
Group Member
Tue 28 Feb 2023 04:03:08 PM UTC, comment #2: 

Works for me on Win10 with ATI mobility 4650 and on
Win11 with Intel UHD 630. The latter would hang if I try to print() this or anything else, so I usually have it set to software OpenGL driver.


Dmitri A. Sergatskov <dasergatskov>
Tue 28 Feb 2023 03:32:54 PM UTC, comment #1: 

Works for me with 8.0.90 on Windows 11 with the following renderer:

>> __opengl_info__
   version: 4.6.0 NVIDIA 528.49
    vendor: NVIDIA Corporation
  renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2

Markus Mützel <mmuetzel>
Group Member
Tue 28 Feb 2023 03:07:50 PM UTC, original submission:  

Try this:

plot ([2, 2], [2, 4], 'linestyle', ':', 'linewidth', 1.5)

Octave-7.3.0 plots this fine. Octave-8.0.91 & dev Octave crash using system OpenGL.
Switching to the Octave-supplied 0penGL.dll avoids the crash.

I wouldn't expect a crash with such a basic graphics command.
The 'linewidth' property seems to be the culprit; leaving it out I see no crash either.

Ryzen 7 5800U with Radeon graphics.

Philip Nienhuis <philipnienhuis>
Group Member


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by dasergatskov (Posted a comment)
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by philipnienhuis (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only project members can vote.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.12