[Octave-bug-tracker] [bug #47326] segfault in GUI and interpreter initialization

[Mike Miller]

Update of bug #47326 (project octave):

                  Status:                    None => Patch Submitted        

    _______________________________________________________

Follow-up Comment #6:

Thanks for the report, that certainly indicates that there are some threading
problems in the initialization. While the stack is not exactly the same, my
crash could have occurred after some earlier interaction.

My understanding of the GUI is that Qt has to run in the main thread, so it
starts another thread to run the interpreter and talks to it over the
octave_link class. This thread is starting while the GUI is still being
constructed, though, and before QApplication::exec is called.

The following patch defers execution of the interpreter until after the
QApplication main loop is running, and this seems to work better for me so far
(running for 30 minutes now without a crash).

I'm also not that comfortable with the GUI so I'd appreciate someone who works
on it more to see if this is safe, maybe test on Windows also.

(file #36598)
    _______________________________________________________

Additional Item Attachment:

File name: delay-interp.diff              Size:0 KB


    _______________________________________________________

Reply to this item at:

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

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