[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #48361] Segmentation fault with Qt figures
From: |
Guillaume |
Subject: |
[Octave-bug-tracker] [bug #48361] Segmentation fault with Qt figures |
Date: |
Fri, 1 Jul 2016 11:38:52 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 |
URL:
<http://savannah.gnu.org/bugs/?48361>
Summary: Segmentation fault with Qt figures
Project: GNU Octave
Submitted by: gyom
Submitted on: Fri 01 Jul 2016 11:38:50 AM GMT
Category: Plotting
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Crash
Status: None
Assigned to: None
Originator Name: Guillaume
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: GNU/Linux
_______________________________________________________
Details:
I suddenly observe very frequent segfault when opening figures - I would say
this is related to a change in dev over the last week or so.
At the moment, running this:
F = figure(...
'Position',[659 20 767 1105],...
'Visible','off');
figure(F)
results in this:
>> testfigure
>> panic: Segmentation fault -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
Segmentation fault
or sometimes the figure becomes visible and unresponsive - Octave has to be
killed.
It even seems that running something as simple as this:
figure('position',[659 200 767 421])
creates an unresponsive figure. If the 'position' property is not set up, it
works as usual.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?48361>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #48361] Segmentation fault with Qt figures,
Guillaume <=