On 06/30/2014 06:54 PM, Pavel Sanda wrote:
Richard Heck wrote:
Paragraph::write, so the crashing call to to_utf8 could come in any of
them. The crashing call certainly isn't the first one, since "\begin_inset
smells little bit like concurrency problem inside to_utf8.
we might try doing autosave while using to_utf8 somewhere in ui?
I wondered about something like this, too: There was the very big change
in to_utf8, that we
use QThreadStorage to have per-thread storage for the IConvProcessor.
That said, if you look
at the full backtrace, there's no real activity in the other threads.
And people are seeing this on
normal save, too (i.e., no cloning). There's also the fact that we
always seem to see this with
tables....
I don't know if you noticed, but I missed it the first time: It's
reporting a segfault in to_utf8.
What could be causing that? I.e., where is the invalid access?
Richard
