bugGNU Octave - Bugs: bug #53153, MXE octave crash after...


bug #53153: MXE octave crash after introduction of QOpenGLWidget

Submitted by:  Rik <rik5>
Submitted on:  Wed 14 Feb 2018 04:01:03 AM UTC  
Category: Configuration and Build SystemSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Regression
Status: ConfirmedAssigned to: None
Originator Name: Open/Closed: Open
Release: devOperating System: Microsoft Windows

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


(Jump to the original submission Jump to the original submission)

Wed 28 Feb 2018 05:41:24 PM UTC, comment #13:

This issue is still present for me. I have verified that --disable-system-opengl can be used as a workaround. But, the long term solution is probably to choose the correct libGl at installation or runtime. I've changed the category of the bug to "Configuration and Build System".

Rik <rik5>
Project Administrator
Mon 19 Feb 2018 11:43:24 PM UTC, comment #12:

I don't have a bin/libGL.dll. I do have these

Is one of those the correct one to move aside to verify that --disable-system-opengl definitely works?

I tried moving opengl32.dll but then Octave just won't start--it complains about an invalid entry point.

Rik <rik5>
Project Administrator
Sun 18 Feb 2018 09:27:00 PM UTC, comment #11:

Didn't read it carefully but this article may be useful:


Basically, the opengl library which is used by an application can be chosen and loaded dynamically at startup, based on feature tests.

Pantxo Diribarne <pantxo>
Project Member
Sun 18 Feb 2018 05:55:36 PM UTC, comment #10:

Now that you have the binary built with the mesa libGL, you should be able to switch back to the system library by moving bin/libGL.dll aside. If you try that, then Octave should still run and show you the same problem you had originally.

If that works as I expect, then maybe we should build libGL by default. Then the choice of whether to use it could be made when Octave is installed. Or possibly even when running Octave by putting libGL in a separate directory and then having the octave.vbs wrapper script add that directory to the PATH (on Windwos, I believe that makes a DLL available) before launching the actual Octave binary.

John W. Eaton <jwe>
Project Administrator
Sun 18 Feb 2018 06:12:37 AM UTC, comment #9:

Yes, the option --disable-system-opengl works for me, but how would someone downloading an Octave installer know to get the version that was comppiled with SW rendering versus the regular one?

Rik <rik5>
Project Administrator
Fri 16 Feb 2018 09:13:35 PM UTC, comment #8:

This is qt5, 32-bit system. I'll try rebuilding with --disable-system-opengl.

Rik <rik5>
Project Administrator
Fri 16 Feb 2018 06:30:42 AM UTC, comment #7:

Is this with qt4 or qt5?

I don't see this issue with my build on a Windows 10 system installed directly on hardware or a Windows 7 system running in a VM.

Are you using the OpenGL libraries provided by your Windows installation and possibly hardware drivers?

Could you build with --disable-system-opengl? I think that should enable mesa and give you a libGL that will do software rendering using the "softpipe" driver. Does that avoid the crash?

John W. Eaton <jwe>
Project Administrator
Fri 16 Feb 2018 12:26:04 AM UTC, comment #6:

The changeset that introduced the crash is

Just guessing, but there may be some additional initialization that QOpenGLWidget requires that we are not doing.

Rik <rik5>
Project Administrator
Thu 15 Feb 2018 12:35:22 AM UTC, comment #5:

I've established that the plotting issue appeared between 8/31/17 and 11/17/17. I'm going to concentrate on bisecting that window for this bug report.

However, along the way I found that the truncated initial message in the Command Window was introduced in the window from 11/17/17 to 1/1/18. That might be helpful to you (jwe).

Rik <rik5>
Project Administrator
Wed 14 Feb 2018 11:01:49 PM UTC, comment #4:

It's tedious, but I used hg to go back to 8/31/17 and this cset

I then built dist-gzip, transferred the gzip file over to MXE and built that. Finally I tested that version in the same Windows XP virtual machine.

The good news is that plotting works AND the initial message in the Command Window is not truncated. Ergo, there must have been changes in the last 5.5 months that caused these regressions. The bad news is that the compile/test cycle is very long and bisection could take a few days to locate the problem cset.

Rik <rik5>
Project Administrator
Wed 14 Feb 2018 05:39:45 AM UTC, comment #3:

32-bit installer. The configure line for MXE is

Rik <rik5>
Project Administrator
Wed 14 Feb 2018 05:08:46 AM UTC, comment #2:

I tried the 32-bit installer generated by the buildbot on a Windows 7 system running in a VM and sombrero worked for me. Just to be sure, I tried plot (1:10) and it also worked. I can try a 64-bit build once one of the builds finishes.

John W. Eaton <jwe>
Project Administrator
Wed 14 Feb 2018 04:56:05 AM UTC, comment #1:

Which configuration? 32-bit Windows, 64-bit Windows with the default 32-bit Fortran integers, or 64-bit Windows with 64-bit Fortran integers?

John W. Eaton <jwe>
Project Administrator
Wed 14 Feb 2018 04:01:03 AM UTC, original submission:

Running on a Windows XP VM and self-compiled MXE Octave


causes a crash.

However, when using FLTK as the toolkit there is no problem.

Rik <rik5>
Project Administrator


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

Attach File(s):

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by pantxo (Posted a comment)
  • -unavailable- added by jwe (Posted a comment)
  • -unavailable- added by rik5 (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed 28 Feb 2018 05:41:24 PM UTCrik5CategoryOctave Function=>Configuration and Build System
    Fri 16 Feb 2018 12:26:04 AM UTCrik5SummaryMXE octave crash with any plot=>MXE octave crash after introduction of QOpenGLWidget
    Wed 14 Feb 2018 11:01:49 PM UTCrik5StatusNone=>Confirmed

    Back to the top

    Powered by Savane 3.1-cleanup1