Peter Kümmel wrote: >> Peter, i dont understand one thing. if i try to reproduce Liviu's >> problems, >> i see that view buttons get disabled when the export is done. that means >> that we actually prohibit more threads to run together. > > But we update the status bar or the progress widget while exporting is busy > and there, I assume, iconv() was called.
yes, now i talk only about crashes having getPath in backtrace, not iconv, these should be fixed definitely. >> isn't then this graph path bug just sideffect of disabling buffer-view >> lfun >> too late, ie more threads starts when pressing lot of ctrl+t/d before we >> block the lfun. then - instead of crazy safeguarding of graph class we >> could just put some block early in buffer-view lfun, no?. > > I don't know why getPath is called by several threads, but when it's > because > the user has started more than one, your idea could help. what about putting one mutex in the beginning of buffer-view instead of twenty of them inside graph code? pavel
