Re: wxt file-save oddity

[sfeam <sf...@us...>]

On Saturday, 15 November 2014 03:07:27 PM Allin Cottrell wrote:
> On Sat, 15 Nov 2014, sfeam wrote:
> 
> > On Saturday, 15 November 2014 01:54:32 PM Allin Cottrell wrote:
> >>> On 11/15/2014 11:55 AM, Allin Cottrell wrote:
> >>>> On Sat, 15 Nov 2014, Daniel J Sebald wrote:
> >>>>
> >>>>> On 11/15/2014 11:36 AM, Allin Cottrell wrote:
> >>>>>> I just tried out the file save button in the gnuplot wxt window. It
> >>>>>> works nicely... except that I'm seeing a delay of up to 40 seconds
> >>>>>> between clicking the button and the file-save dialog opening.
> >>>>>>
> >>>>>> This is on a lightly loaded system, with gnuplot launched via
> >>>>>> gnuplot -persist<plotfile>.
> >>>>>
> >>>>> What operating system?
> >>>>
> >>>> Arch Linux. No other programs showing odd delays in response.
> >>
> >> Aha. No such problem if I run gnuplot interactively, load the plot
> >> file and display the plot. Then the Save button works instantly. The
> >> loooong delay just happens when gnuplot is run with -persist.
> >
> > In that case it might be informative to establish where the
> > program is hung/delayed.
> > Fire up gnuplot -persist, determinine its <pid>, then hit
> > the problematic button.
> > While it is in the hung state, from another terminal run
> > $ gdb -p <pid>
> > gdb> where
> >
> > to establish where the code is hung.
> 
> OK, I'm attaching the output from this.
> 
> Allin Cottrell

I can reproduce this now, so at least I can investigate as I find time.
No ideas at the moment, other than it may indicate an interlock failure
in the gvfs/dbus library code.  We could report that upstream to gtk,
but I am afraid that we would then run into the problem that upstream
development is focused on gtk3, while the problem is occurring in 2.8.

I suppose we could disable the Export-to-File widget in persist mode,
but that would be unfortunate.  

	Ethan