bugGNU Octave - Bugs: bug #46885, Octave crashes on click in image...

 
 

bug #46885: Octave crashes on click in image display window

Submitter:  None
Submitted:  Tue 12 Jan 2016 11:33:20 PM UTC
   
 
Category:  Plotting with OpenGL Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Duplicate Assigned to:  None
Originator Name:  Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 4.0.0
Operating System:  * Microsoft Windows Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 23 Feb 2016 12:16:39 AM UTC, comment #14: 

I think still open bug #45863, which you also heavily commented on, covers the problem relevant to your system. That it is specific to the Qt toolkit and that it seems related to the Mesa drivers for an Intel HD graphics chipset. And any history here won't be lost whether the bug is open or closed.

Mike Miller <mtmiller>
Group Member
Mon 22 Feb 2016 11:07:44 PM UTC, comment #13: 

OK. Do you want a new bug report?

I do not think that this is the same as #45372.

There is quite a bit of history of this bug below,
so whatever choice you make it would help not to
lose that.


Michael Godfrey <godfrey>
Group Member
Mon 22 Feb 2016 10:57:23 PM UTC, comment #12: 

Michael: I don't doubt that you are still seeing a crash with the Qt toolkit on your video card, but this bug report was about a crash on Windows 7 when clicking on an image plot (please see originator's comment). That bug has definitely been fixed, see bug #45372.

Mike Miller <mtmiller>
Group Member
Mon 22 Feb 2016 10:36:35 PM UTC, comment #11: 

I just tried:

>> graphics_toolkit('qt')
>> plot(1:600)
>> panic: Segmentation fault -- stopping myself...

attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
Segmentation fault (core dumped)
[godfrey@pbdsl4 EMandG_New]$

Is using current version 4.1.0+

So, the problem still exists. There is no
problem when using fltk. So, there is an important
difference between qt and fttk.


Michael Godfrey <godfrey>
Group Member
Mon 22 Feb 2016 05:59:38 PM UTC, comment #10: 

No response from OP in several weeks, let's consider this resolved with 4.0.1 (bug #45372 I believe).

Mike Miller <mtmiller>
Group Member
Sun 24 Jan 2016 02:36:53 PM UTC, comment #9: 

@Pantxo: Just a reminder that this seg fault ONLY
occurs for qt. It NEVER occurs for fltk. So, one
approach would be to inspect the differences between
qt and fltk. They are supposed to be similar and in
fact someday are supposed to be merged. In any case
something that qt does and fltk does not do is causing
the seg fault. I also, just tried the test with the current
dev build and the behavior is unchanged. Under qt moving
the figure and then clicking on it reliably causes the
seg fault.

Michael Godfrey <godfrey>
Group Member
Fri 15 Jan 2016 10:16:25 AM UTC, comment #8: 

@Pantxo: I just ran another test NOT including
the visible off; print xxx.pdf; visible on;
sequence and the same procedure as before causes
the same seg fault! So, this is unconnected with
the seg fault due to print xxx.pdf

Michael Godfrey <godfrey>
Group Member
Fri 15 Jan 2016 01:29:11 AM UTC, comment #7: 

@Pantxo: One final observation. At one point I could
click on the "annotate (ABC)" button and an annotate
box appeared. Now I cannot reproduce that. Clicking on
the annotate button only changes its background...

Michael Godfrey <godfrey>
Group Member
Fri 15 Jan 2016 01:24:12 AM UTC, comment #6: 

Pantxo: One correction. I only have to drag the figure
and then click repeatedly on the figure to cause the seg
fault. If I do not drag the figure first the seg fault
does not occur. It appears not to be the drag itself,
but the subsequent clicking that causes the seg fault.


Michael Godfrey <godfrey>
Group Member
Fri 15 Jan 2016 01:14:47 AM UTC, comment #5: 

@Pantxo:  I used fltk for a while without problems, so
I switched back to qt and almost immediately got seg fault.
So, I ran under gdb and only had to try twice to get the
seg fault that is attached. The procedure was:
1. run script which generated a plot and did a print xxx.pdf
   enclosed in visible off print visible on.
2. As soon as the figure reappeared click-hold on it and
   drag it across the screen. The motion evidently caused the
   seg fault.
You will notice that near
the beginning are messages from mesa saying this is a
mesa error, with bug reporting instructions. Several months
ago I reported the crash if you use print with the figure
visible (which I think is related to this failure), but I
have never heard anything back from them. Since you can
better explain what the octave code is trying to do, could
you submit a report?

My system is:
Octave 4.1.0+
hg summary
parent: 21074:9ff2ae6cd5b0 tip
 rework fatal flex error handler (bug #46877)
branch: default
bookmarks: *@
commit: 8281 unknown (clean)
update: (current)

computer: Intel NUC5i5RYH (this uses the Intel HD 6000 graphics)
software: current Fedora 23, most of mesa is at:
mesa-libEGL-11.1.0-1.20151218.fc23.x86_64, but I notice
that: mesa-libGLU-9.0.0-9.fc23.x86_64
and mesa-libGLU-devel-9.0.0-9.fc23.x86_64
are also the fedora 23 current versions.
The kernel is: kernel-4.3.3-300.fc23.x86_64
(This kernel is actually relatively stable - no problems
since it was installed. The previous kernel seg faulted
under heavy video load.)

So, tell me if you need more information.
The dump is attached.

(file #36039)

Michael Godfrey <godfrey>
Group Member
Thu 14 Jan 2016 01:22:33 PM UTC, comment #4: 

@Pantxo: It is possible that this is really bug #45863
because I think that the crashes occurred just after
a visible off print xxx visible on sequence. But the
crash actually happened when I was moving the plot
window on the screen. The print had completed normally.
So, I suspect that it is this bug.

I switched back to fltk and, doing the same kind of thing,
i.e. running a script that does a print xxx.pdf, and then
moving the plot window, and have had no more crashes so
far. I will try some more work using fltk and if no crashes
switch back to qt. OK? This is pretty hard to isolate or
run under gdb since it only happens occasionally and not
predictably.

Also, I am very short of time just now and travelling next week.
Sorry.

Michael Godfrey <godfrey>
Group Member
Thu 14 Jan 2016 08:03:21 AM UTC, comment #3: 

@Michael: are you experiencing crashes while clicking on images specifically or may this still be bug #45863?

Pantxo Diribarne <pantxo>
Group Member
Wed 13 Jan 2016 11:51:46 PM UTC, comment #2: 

This may not be the same bug as the one reported under Windows,
but I recently switched from fltk to qt plotting and I now
occasionally experience Octave seg fault when clicking
on a plot window. It does not happen often so it is hard
to try to capture under gdb.

First, I will try switching back to fltk.

My system is Fedora 23 with current updates and current
dev Octave.

Michael Godfrey <godfrey>
Group Member
Wed 13 Jan 2016 04:09:37 PM UTC, comment #1: 

Indexed images and more generally images represented by non-double types used to crash Octave when clicking (in Qt graphics_toolkit only) but this has been fixed and the soon coming bugfix release 4.0.1 will not trigger the bug anymore.

What does "whos img" return in your example?

Pantxo Diribarne <pantxo>
Group Member
Tue 12 Jan 2016 11:33:20 PM UTC, original submission:  

Open Octave GUI. In the command window execute

img = imread("bird.png");
imshow(img);

Then click on the window that has opened. -> Octave closes.

OS: Windows 7
Octave: 4.0.0.

Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #36039:  New_plot_seg_fault_150115 added by godfrey (9KiB - application/octet-stream)

 

Digest:
   bug dependencies.

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by godfrey (Posted a comment)
  • -email is unavailable- added by pantxo (Posted a comment)
  •  

    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.

     

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-02-22 mtmiller StatusNeed Info Duplicate
        Open/ClosedOpen Closed
        Dependencies- Depends on bugs #45372
    2016-01-15 godfrey Attached File- Added New_plot_seg_fault_150115, #36039
    2016-01-13 pantxo CategoryGUI Plotting with OpenGL
        Item GroupNone Segfault, Bus Error, etc.
        StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code