Thread: Sigil 0.2.0β2
View Single Post
Old 03-13-2010, 11:47 AM   #27
Valloric
Created Sigil, FlightCrew
Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.
 
Valloric's Avatar
 
Posts: 1,982
Karma: 350515
Join Date: Feb 2008
Device: Kobo Clara HD
Quote:
Originally Posted by tlrowley View Post
I was happily playing with the first .2 beta, but this second version is giving me fits.

After running into the wait-state error that was talked about in the other thread (twice, losing my edits both times), I tried a very simple test - I opened a file and tried to save it. This very reliably crashes/hangs for me whether I do a "save" or "save as". Of course, if I use "save" I lose the original file, never a good option. If I simply open Sigil and save the empty/default file it works.

I'm on Mac 10.6.2 - what info can I provide to help debug? I very impressed with Sigil and I've found it very useful.
The crash-on-save has been reported, and I still can't reproduce it. I've added a mechanism that should print out a detailed error message when such a crash occurs with instructions to report it on the tracker. That dialog should contain valuable debug information. So far, no one has posted this debug info, including the original issue reporters.

The deadlock bug(s)... when I see them, I fix them. It's not hard. But I have to see them. The last time I saw one was a couple of weeks ago.

If you can get the deadlock to reproduce with a sequence of repeatable steps, then report that on the tracker and I'll fix it (more info here). I've said this countless times, I cannot fix a bug I cannot see. Issue reporters have to provide the necessary information to help me see the bug, and that's it. The more info, the better.
Valloric is offline   Reply With Quote