Do you guys even open your own software? I followed your convoluted "fix" to constant crashing, it lasted for one session only. No, I am not going to send crash reports. Open your own software. This thing is not even Alpha software standard. Shame on you for accepting money for this.
Dear God! Stop the beachball
@EvilDrGrumpyDad those "reset" instructions really help with pretty specific situations and may not have really done anything but hide the particular issue you have been hit – the best way for us to resolve system specific crashes and hangs is by us receiving the diagnostic info that lets us specifically look into issues, which involve crash reports and the document in question sent to email@example.com, if that's a possibility.
The crash rate we observe presently with the 1.1.1 is at less than 1% of the total current app sessions, which overall is encouraging – we are aware of one relatively common source of issues still, which is certain outline modifications sometimes leading to instability still. We have been working on this for this week and hope to bring significant improvements in the next update next week on this, solving the great majority of remaining sources of crashing. However, again, diagnostic information helps us a lot and we don't ask it because we treat you as a tester, we ask it because the space of possible documents you can write this tool is infinite and there are parts of that space we simply have not visited as the developers – the diagnostic output has helped us reach the < 1% overall crash rate and it helps us hopefully in the next update even much further.
@mz2 What do you count as crashes? Because I have encountered many occasions where I have had to force-quit Manuscripts because it has stopped responding - perhaps these are not counted as crashes in your diagnostic data? Also, I still need to force quit the app whenever I want to quit without saving changes, otherwise it goes into an infinite loop, which is not ideal.
@olibclarke could you do the following if you observe beachballing, please:
- Open the Activity Monitor app (which you find inside your Applications folder under Utilities)
- Select Manuscripts (it should appear in red) in the list of applications.
- click on the "i" button at the top
- Take a "sample"
- Save the sample and send us the file via firstname.lastname@example.org
That should allow us to see what the app is doing while it hangs.
Also, does the Console.app (which you also find inside your Applications folder under Utilities) output any Manuscripts related error messages?
Beachballing doesn't get reported by the crash reporting tool in the same way, hence requesting this separately, but we do have something in the works that should improve the situation in this regard (it is pretty closely related to a remaining sources of instability too).
To be honest: The app really is buggy. It Crashes many times and i also feel like a alpha-tester. Anyway I really like the concept and try to support you by Sending you errors and today i went through the support forum to post some missing features. It would be a great gesture from your side if you would give all your 1.0 users a free upgrade as soon as the first major update comes close…
Yeah, I'd also say it's really buggy. What I can do now is just placing it in the "potential productivity folder". It's very unstable for either importing a word document or just write in it. Please hope we can get a free major update later. It's just unusable now.
@Rover if you experience any problem at all with Word importing, sending us the file helps us a lot. This helps us because the MS Word file format is huge (it's covered in an over 4,000 page specification document) – we obviously cover a big range of Word documents but there are for sure situations still where we don't either import some detail you would like imported, or indeed it is possible for the app to crash in such situations.
@mynona we will continue to make free updates to all license holders and continue adding both new functionality and overall polish.
Thanks God! There is not only me encounter this problem. I have to force-quit app and reopen it during editing my paper. It's an awful experience.
I think the reliability is the most emergent issue what the developer should concern on.
I have the spinning beach ball problem too. It seems connected to a citation compiler step that hangs indefinitely. It seems connected to the fact that, although I started to add a citation, I never did. IOW, it seems connected to Manuscripts trying to find citations in my document that do not exist or do not have a linked citation database.