Jump to content

9 Crash on Startup


Helen Brown

Recommended Posts

If you successfully upgrade to version 9, but then it crashes when you start up, please try removing the Startup session from user/Library/Preferences/Accordance Preferences. This has fixed everyone's problems.

 

We would like to see a Startup session that has this problem, before it does so. So if you have one, or can make a backup of one, that subsequently did become corrupt, please zip it and post it or send it to me or Joel.

Link to comment
Share on other sites

If you successfully upgrade to version 9, but then it crashes when you start up, please try removing the Startup session from user/Library/Preferences/Accordance Preferences. This has fixed everyone's problems.

 

We would like to see a Startup session that has this problem, before it does so. So if you have one, or can make a backup of one, that subsequently did become corrupt, please zip it and post it or send it to me or Joel.

Here are two startup sessions. Both crashed. I removed one. Tried it. A9 crashed. When I looked in the preferences again, there was another one. So, not sure why there are two. I renamed the second one.

Accordance Startup Sessions.zip

Link to comment
Share on other sites

On startup Accordance 9 was not responding for about 30 seconds and then would pop up the error: Memory error # -116 in procedure "ChangeHandle"!

 

Console logs were as follows:

9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	An unhandled exception occurred at $002DC176 :
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	EAccessViolation : Access violation
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $002DC176
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $002DB7D9
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $002DB075
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $002DD633
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $002E4848
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $0010B2F3
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $00106B55
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $00106BC1
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $00281C0F
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $00280E63
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $00280750
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $00280617
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $002806D2
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $00280A90
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $00
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	280750
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $00284116
9/22/10 6:04:31 AM	[0x0-0x55055].com.OakTree.Accordance[2071]	  $0029E8CA
9/22/10 6:04:31 AM	com.apple.launchd.peruser.501[83]	([0x0-0x55055].com.OakTree.Accordance[2071]) Exited with exit code: 217

 

I moved the Startup Session file to the desktop as suggested and Accordance 9 started up just fine. However, the workspace was not correct. So, I opened my saved workspace and then Accordance 9 quit immediately.

 

Here is the console message that appeared after that immediate quit:

 

9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	An unhandled exception occurred at $945AC80D :
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	EAccessViolation : Access violation
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $945AC80D
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $9611C76E
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $9611C31C
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $961541B4
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $9616C617
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $9617706B
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $00325A62
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $00325AF4
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $002EC17F
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $002E427D
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $0001CBC0
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $0009F627
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $00012D05
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $0001128F
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $0028063F
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $002806D2
9/22/10 6:05:31 AM	[0x0-0x56056].com.OakTree.Accordance[2121]	  $00280A90
9/22/10 6:05:31 AM	com.apple.launchd.peruser.501[83]	([0x0-0x56056].com.OakTree.Accordance[2121]) Exited with exit code: 217

 

I reopened Accordance 9 again and it showed the same (wrong) workspace so I tried to open my saved workspace again. This time it worked. Then I quit Accordance 9 (which created a new "Startup session" file) and then launched Accordance 9. Again it is hung and gave the same memory error. This appears to be a never-ending sequence of events, so it should be reproducible. There don't appear to be any other diagnostic logs generated for these failures. There is one for earlier in the morning for Accordance 9, but I'm not sure what happened to produce it (no new ones were created in my testing of this problem).

Startup session.zip

Link to comment
Share on other sites

Hi Darrik,

 

On startup Accordance 9 was not responding for about 30 seconds and then would pop up the error: Memory error # -116 in procedure "ChangeHandle"!

 

I was able to reproduce the 30 second (or so) delay and Memory error with your Startup Session. There appears to be a problem with displaying a picture tab(Uruk?) in your startup session and we should be able to fix this for the next release.

 

 

I reopened Accordance 9 again and it showed the same (wrong) workspace so I tried to open my saved workspace again. This time it worked. Then I quit Accordance 9 (which created a new "Startup session" file) and then launched Accordance 9. Again it is hung and gave the same memory error. This appears to be a never-ending sequence of events, so it should be reproducible. There don't appear to be any other diagnostic logs generated for these failures. There is one for earlier in the morning for Accordance 9, but I'm not sure what happened to produce it (no new ones were created in my testing of this problem).

 

You should not use the attached startup session until we release 9.0.3. In the mean time, are you able to reproduce this session in a new workspace?

 

Mike

Link to comment
Share on other sites

Now I'm having trouble opening that old workspace without A9 immediately crashing, so I don't recall everything I had in the workspace. In trying to recreate it I don't appear to be able to add Maps as a tab (get a warning that there is not enough space to move this item into the workspace or zone).

 

Is the Workspace and the Session startup identical? The file sizes were the same, so I assume they are quite close if not the same. In that case you should be able to see the problem I have in trying to open that workspace/session (immediately quits). In the mean time, I have a similar workspace I just created that doesn't cause the hang on launch, so I'm good to go right now.

 

Thanks for looking into this issue.

Link to comment
Share on other sites

Hi Darrik,

 

I was also seeing a crash when trying to load your startup session. There were a couple of problems when trying to display the picture tab with corrupted information. I am not sure why the information was corrupted and we will do our best to prevent Accordance from crashing. I will be using your startup session (among others) for further investigation.

 

I am sorry we are not able to help you more at this time. Let us know if you come across another saved session that is causing a crash when loading.

 

Mike

Link to comment
Share on other sites

  • 3 weeks later...

I'm using Acc-9 (OS 10.6.4) .... When I start-up Accordance, I immediately see the following message (Acc doesn't load, only the message is displayed). Note that this message is repeatable. Early this morning was the first I've noticed the message:

"This version of Accordance does not support folders in Favorite Modules of Favorite Workspaces.

To use Favorites in this version of Accordance, you will need to remove all folders from Favorite Modules and Favorite Workspaces. "

Once I click on the OK button to acknowledge the error, the "last session" that I was using doesn't load. I have to explicitly load a workspace by going under "My Workspaces."

I removed the "startup session" file under user/Library/Preferences/Accordance Preferences and restarted Acc 9 several times, but this doesn't help.

Helen, I've sent you the console messages directly.

Thanks

LW3

Link to comment
Share on other sites

I think you will need to remove the Favorites settings file as well, at least rename it, and if that doesn't work, the User Groups file as well.

 

There is no point in sending the logs as a personal message. They get truncated and are rarely helpful in any case. Please do not send us logs unless we specifically request them.

Link to comment
Share on other sites

I renamed the Favorite folder under Accordance Preferences and that worked!!!!!

 

Thank you!

 

The error messages have disappeared!

 

LW3

Link to comment
Share on other sites

Good, but I am afraid that you will need to recreate the Favorites by adding back the saved workspaces that you had in there. The files themselves should have been saved in user/Documents/Accordance files.

Link to comment
Share on other sites

I created sub folders under "My Workspaces"over the weekend which seem to be causing the problem. I'm sure why unless subfolders are not supported in "My Workspaces."

 

Nonetheless, after I eliminated the them, the problem went away. I can successfully quit and restart Accordance without any reoccurring error messages.

 

At least for now, I will ignore creating subfolders.

 

Thanks!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...