bugGNU Octave - Bugs: bug #51922, GUI freezing at startup or Signal...

 
 

bug #51922: GUI freezing at startup or Signal 11

Submitter:  Dan Sebald <sebald>
Submitted:  Sat 02 Sep 2017 07:35:30 PM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  None Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 13 Nov 2017 05:45:03 PM UTC, comment #2: 

I've not seen it again since.  Probably a gremlin due to rapid development changes.  I'm guessing at the time it seemed a tricky thing to track down (one of those random occurrence sort of things) so I just wanted to make a note of the first time I saw it.  Even if this bug does re-emerge I'll still know when it started from this trail, so closing is fine.

Dan Sebald <sebald>
Mon 13 Nov 2017 04:43:35 PM UTC, comment #1: 

@Dan: Is this still a problem?  Or was it a gremlin that has gone away now that we've had another two months of code check-ins.

Rik <rik5>
Group administrator
Sat 02 Sep 2017 07:35:30 PM UTC, original submission:  

I've had the GUI freeze at startup, in what looks like a timing issue (or maybe state at previous exit issue).  I'm just noting that it is version

changeset:   23994:8785b3717140
date:        Fri Sep 01 15:35:17 2017 -0700

which doesn't mean that changeset is the source of error, just a timestamp in case someone else sees this same issue to help pin down when it may have started.

The behavior is that I launched the GUI, indirectly via the build as follows:


sebald@ ~/gardening/white_mold_on_soil $ /usr/local/src/octave/octave/build1/run-octave
sebald@ ~/gardening/white_mold_on_soil $ /usr/local/src/octave/octave/build1/run-octave
octave exited with signal 9
sebald@ ~/gardening/white_mold_on_soil $ /usr/local/src/octave/octave/build1/run-octave
sebald@ ~/gardening/white_mold_on_soil $ /usr/local/src/octave/octave/build1/run-octave
sebald@ ~/gardening/white_mold_on_soil $ /usr/local/src/octave/octave/build1/run-octave
octave exited with signal 11
sebald@ ~/gardening/white_mold_on_soil $ /usr/local/src/octave/octave/


I believe where it indicates "signal 9" is that upon launch the System/GTK window outline appeared in which the graphics memory had the background image (the common scenario in which the screen of video memory is captured and shifted a half dozen pixels) but otherwise was suspended waiting for Octave GUI to fill in the framework windows, but it never happened.  So I forced the application to quit via the GTK panel that holds the application icons.  That is probably when the "octave exited with signal 9" appeared, i.e., bad exit.

Where the "signal 11" is indicated, Octave GUI just exited immediately without any appearance of GTK window area.

Dan Sebald <sebald>

 

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

Attach Files:
   
   
Comment:
   

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 rik5 (Posted a comment)
  • -email is unavailable- added by sebald (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 group members can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-11-13 rik5 Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code