Am Mittwoch, 16. Mai 2018 00:10:34 CEST schrieb Scott Kostyshak
:
> On Wed, May 02, 2018 at 04:00:12PM +, Scott Kostyshak wrote:
> > On Wed, May 02, 2018 at 01:06:04PM +, Jean-Marc Lasgouttes wrote:
> > > Le 28/04/2018 à 00:06, Scott Kostyshak a écrit :
> > > > On Wed, Apr 25, 2018 at 06:4
On Wed, May 02, 2018 at 04:00:12PM +, Scott Kostyshak wrote:
> On Wed, May 02, 2018 at 01:06:04PM +, Jean-Marc Lasgouttes wrote:
> > Le 28/04/2018 à 00:06, Scott Kostyshak a écrit :
> > > On Wed, Apr 25, 2018 at 06:41:36PM +, Scott Kostyshak wrote:
> > >
> > > > it is not 100% reproduc
Le 28/04/2018 à 00:06, Scott Kostyshak a écrit :
On Wed, Apr 25, 2018 at 06:41:36PM +, Scott Kostyshak wrote:
it is not 100% reproducible for me. I wonder if valgrind might be useful
to try in this situation.
Attached is a valgrind log. Do the invalid reads provide any clues?
Does this
Le 29 avril 2018 05:31:46 GMT+02:00, Richard Kimberly Heck a
écrit :
>>There's some kind of race condition involved, then, it seems to me. But
>I think the general idea
>JMarc had must be right. It's just that we only get the unfortunate
>paint event sometimes.
>
>
I will take care of this one
On 04/28/2018 11:35 AM, Scott Kostyshak wrote:
> On Sat, Apr 28, 2018 at 01:58:41PM +, Richard Kimberly Heck wrote:
>> On 04/28/2018 07:58 AM, Jean-Marc Lasgouttes wrote:
>>> Le 28/04/2018 à 02:09, Richard Kimberly Heck a écrit :
I'm not good at reading these things, but I do see several
>
On Sat, Apr 28, 2018 at 01:58:41PM +, Richard Kimberly Heck wrote:
> On 04/28/2018 07:58 AM, Jean-Marc Lasgouttes wrote:
> > Le 28/04/2018 à 02:09, Richard Kimberly Heck a écrit :
> >> I'm not good at reading these things, but I do see several
> >> lyx::InsetInclude::~InsetInclude(), which
> >>
On 04/28/2018 07:58 AM, Jean-Marc Lasgouttes wrote:
> Le 28/04/2018 à 02:09, Richard Kimberly Heck a écrit :
>> I'm not good at reading these things, but I do see several
>> lyx::InsetInclude::~InsetInclude(), which
>> would presumably be the inset that's being replaced. So it might be some
>> kind
Le 28/04/2018 à 02:09, Richard Kimberly Heck a écrit :
I'm not good at reading these things, but I do see several
lyx::InsetInclude::~InsetInclude(), which
would presumably be the inset that's being replaced. So it might be some
kind of double delete
issue? Then again, a lot of the log seems to r
On 04/27/2018 06:06 PM, Scott Kostyshak wrote:
> On Wed, Apr 25, 2018 at 06:41:36PM +, Scott Kostyshak wrote:
>
>> it is not 100% reproducible for me. I wonder if valgrind might be useful
>> to try in this situation.
> Attached is a valgrind log. Do the invalid reads provide any clues?
I'm not
On Wed, Apr 25, 2018 at 06:41:36PM +, Scott Kostyshak wrote:
> it is not 100% reproducible for me. I wonder if valgrind might be useful
> to try in this situation.
Attached is a valgrind log. Do the invalid reads provide any clues?
Scott
==4977== Memcheck, a memory error detector
==4977== Co
On Tue, Apr 24, 2018 at 11:00:46PM +, Richard Kimberly Heck wrote:
> On 04/24/2018 01:10 AM, Scott Kostyshak wrote:
> > I can reproduce on master and on 2.3.x.
> >
> > To reproduce:
> >
> > 1. download the attached 3 documents and put them in the same directory.
> > 2. open master_copy_from.lyx
On 04/24/2018 01:10 AM, Scott Kostyshak wrote:
> I can reproduce on master and on 2.3.x.
>
> To reproduce:
>
> 1. download the attached 3 documents and put them in the same directory.
> 2. open master_copy_from.lyx in one LyX instance
> 3. in the dialog that comes up, click "cancel"
> 4. open maste
On 04/24/2018 01:10 AM, Scott Kostyshak wrote:
> I can reproduce on master and on 2.3.x.
>
> To reproduce:
>
> 1. download the attached 3 documents and put them in the same directory.
> 2. open master_copy_from.lyx in one LyX instance
> 3. in the dialog that comes up, click "cancel"
> 4. open maste
13 matches
Mail list logo
