[Octave-bug-tracker] [bug #48669] Segfaults at exit after using OpenGL-based toolkits in --no-gui mode

[Dan Sebald]

Follow-up Comment #9, bug #48669 (project octave):

I picked an old version of Octave a couple weeks back at random:

hg update 22154:ff54e7882863

and rebuilt.  Both FLTK and Qt work fine for the Nouveau driver, no
crashes...(reboot)...With Nvidia driver, both FLTK and Qt create a correct
plot, but use of both toolkits will cause a segmentation fault at exit.

A wild guess, but I'm wondering about the use of OpenGL elsewhere in the
Octave program, its initialization and so on.  I see there is this
opengl_renderer() class.  For example, I'm guessing that OpenGL_fltk class is
using these opengl_renderer routines for drawing the plot.  That is, only an
Fl_Gl_Window is supposed to be using OpenGL commands in FLTK (unless one uses
the route of gl_visual/gl_start/gl_finish in non-Gl FLTK windows

http://www.fltk.org/doc-1.3/classFl.html#a3d21e87ef889306a7be56e94ea0bda10
).  If there is some type of OpenGL initialization done by opengl_renderer()
prior to Fl_Gl_Window constructor, could that cause a conflict?  It would be
like using OpenGL commands outside of Fl_Gl_Window.  I don't know if that is
happening or not as I don't know this opengl_renderer class real well.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48669>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/