CRASH: Proclaim quit suddenly

I was adding and then amending existing content slides to Proclaim when the software suddenly shut down. Proclaim does not appear to have produced a crash log (I have attached what appears to be a historic crash log, just in case I am misreading the contents). I have also attached the Proclaim log.

I am working on a MBA (2011), 13", 256 SSD and an i5 processor.

Please let me know should you require any further information.

Andy

2772.Proclaim_Crash.txt.zip

8540.Proclaim.log.zip

Find more posts tagged with

Comments

Andy

Actually, the same thing has happened again.

Both crashes occurred as a result of reusing and then re-editing content. On the first occasion, I was editing a very simple content slide with plain text in the one text box. On the second occasion, I was editing the title of a .jpeg (inserted into a content slide).

I have uploaded the crash log and Proclaim log.

Please let me know if you need any further information.

I am still working on the MBA (2011).

Andy

6318.Proclaim_Crash.txt.zip

1122.Proclaim.log.zip

Scott Alexander

https://community.logos.com/discussion/comment/332050#Comment_332050

Created a case for this. Thanks for the logs.

Andy

https://community.logos.com/discussion/comment/332090#Comment_332090

Dear Scott,

Just to update you.

I have been trying to build a service in Proclaim for much of tonight and this latest version is next to unusable. The crash reported above is occurring with every other action. I have had to restart seven or eight times. The bug is not limited to the reusing and reediting of slides. I have added bible passages and, when formatting, this is killing the app.

I have not moved to the PC to see whether the experience is better, but I am more than a little concerned about the stability of this version given that we have two services tomorrow.

Andy

Scott Alexander

https://community.logos.com/discussion/comment/332155#Comment_332155

Andy,

I'm noticing the stack trace includes an error related to com.apple.FileSyncAgent.iDisk

Is this a new configuration for your MBA? have you always been using iDisk? are you using iDisk to host your home directory?

We made some changes last week to crash earlier when unhandled exceptions are encountered in the application (just like Windows does). The rationale behind this change is to better identify the root cause of bugs. Previous versions often let the app limp along in a corrupted state causing a multitude of false bug reports. It is possible that this iDisk exception has been happening on your MBA since day one and we just ignored it. We need to spend some time understanding the problem so we can determine whether the exception should be handled by the application.

Andy

https://community.logos.com/discussion/comment/332257#Comment_332257

I'm noticing the stack trace includes an error related to com.apple.FileSyncAgent.iDisk

Is this a new configuration for your MBA? have you always been using iDisk? are you using iDisk to host your home directory?

We made some changes last week to crash earlier when unhandled exceptions are encountered in the application (just like Windows does). The rationale behind this change is to better identify the root cause of bugs. Previous versions often let the app limp along in a corrupted state causing a multitude of false bug reports. It is possible that this iDisk exception has been happening on your MBA since day one and we just ignored it. We need to spend some time understanding the problem so we can determine whether the exception should be handled by the application.

Dear Scott,

Thank you for the response.

Apologies if I sound ignorant, I am new to Mac and just trying to get my head around the differences.

I presume by iDisk, you are referring to the cloud based storage system which proceeded iCloud. If so, I do have access to this and have so since day one. I presume by home directory you are referring to programme files, etc. All I have saved on iDisk is some Word/Pages documents and a few photos. I have not used it often from the Mac and have never imported anything into Proclaim from iDisk.

Apologies if I have missed the point of your question. Please let me know if you need further and more specific information.

I now better understand why the programme is crashing (which is helpful and reassuring).

Thanks again, Scott.

Andy