On 04/27/2018 06:06 PM, Scott Kostyshak wrote: > On Wed, Apr 25, 2018 at 06:41:36PM +0000, 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 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 repeat, and I'm not sure I understand why. Riki
