[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54507] Segfault in QT5 when resizing window d

From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #54507] Segfault in QT5 when resizing window during initialization
Date: Thu, 16 Aug 2018 20:04:12 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

Follow-up Comment #4, bug #54507 (project octave):

There could be something in Octave.  For a half year or more I've been
experiencing a startup crash *only after compilation and build* when working
on a bug, and not every time after compilation.  Instead maybe every tenth or
fifteen time.  I'm using Mint linux.

It's the sort of thing in which, I'm guessing, the OS has to do a bit more
work to locate and load the executable for some reason.  (Maybe find the
program and put it in some hash table for quick future access?  Again, just

Every time I see this crash, I try thinking of a way I could devise a way to
find it, maybe make it occur regularly.  But then I just move on because the
next launch will work fine.

I keep thinking it might have something to do with loading GUI settings from
the previous session, that the long load delay causes the settings to clash
with whatever else is happening at start up.  But again, that is only a
general feeling.

So, the comment here about moving the window makes me wonder.  Window managers
often do some fancy stuff.  For example, it wouldn't surprise me if launching
an application in GTK or whatever redraws a window from tiny to small to
create some neat-o effect.  So, maybe if there is a delay in loading and the
settings restores the window size later than usual, maybe there is a thread
clash of what the Window Manager is doing and what Octave GUI window resize is

If you can make this problem more common than once every one or two days
(which is what I see), it might lead to a route of investigation.  Perhaps
Torsten could give simple instructions for a line to comment out so that the
Octave GUI does not restore settings at start up, then you build and try to
repeat the start-up crashes on FreeBSD; if the crashes go away, that could be
a lead.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]