Jump to content

Tool Set Updating


SteveL

Recommended Posts

Hello,

 

When I try to change a tool set, I get an error message as shown in the attached file.

 

Also, I've been having unexpected and unrepeatable program crashes.

 

Thank you for your help.

-steve.

post-2977-125711553435_thumb.png

Link to comment
Share on other sites

I am not seeing this problem.

 

What version of Accordance and Mac OS do you have? Can you try creating a new Tool set and editing that, and also removing the Tool sets from your user/Library/Preferences/Accordance Preferences in case that file is corrupt, and starting over with a new settings file.

 

We do know that closing a Construct window will crash 8.3.3, but we cannot look for unrepeatable crashes.

Link to comment
Share on other sites

I'm using latest everything, OS and Accordance. I'll try your suggestion when I'm back at my Mac in a couple of days. Thank you Helen. You all are always especially helpful!

Link to comment
Share on other sites

  • 3 weeks later...

I created my first Text and Tool Sets today, and saw this same error dialogue numerous times, with occasional hard crashing of Accordance.

 

Also, my Tool Sets are getting corrupted, I think when I reorder them (the sets that is, not the modules within the sets) after creating more sets than can fit in the list view without causing a scroll bar to appear. It starts with the contents of one set suddenly becoming swapped with that below it; and then this replacement cascades up the list when I try to correct the first swap. (Hope this makes sense; I've attached screen shots showing how e.g. 1) my "Latin Tools" set came to have the contents of the "Apparati" set below it, 2) how this extended up the set list two more slots to my "Hebrew Tools" set, and 3) how the "Apparati" set came to have the contents of the "References" set below _it_. ) I tried this twice, and both times, after _much_ time spent creating the sets I want, they end up corrupted and unusable. Frustrating.

 

Technical details appended below.

 

Carl

 

Using Accordance 8.4, OS X 10.6.2

 

1) post-84-125860259163_thumb.png

 

2) post-84-125860262256_thumb.png

 

3) post-84-125860267233_thumb.png

 

 

In the system console, I see 20 or so of these entries:

 

11/18/09 10:28:33 PM Accord[13608] *** __NSAutoreleaseNoPool(): Object 0x7c2370 of class NSCFArray autoreleased with no pool in place - just leaking

 

and then:

 

11/18/09 10:30:59 PM Accord[13608] kCGErrorIllegalArgument: _CGSFindSharedWindow: WID 21149

11/18/09 10:30:59 PM Accord[13608] kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

11/18/09 10:30:59 PM [0x0-0x792792].com.OakTree.Accordance[13608] Wed Nov 18 22:30:59 Carl-Hostetters-MacBook-Air.local Accord[13608] <Error>: kCGErrorIllegalArgument: _CGSFindSharedWindow: WID 21149

11/18/09 10:30:59 PM Accord[13608] kCGErrorIllegalArgument: CGSGetWindowTags: Invalid window 0x529d

 

and eventually:

 

11/18/09 10:34:52 PM Accord[13608] kCGErrorIllegalArgument: CGSRemoveWindowFromWindowMovementGroup: Invalid window

11/18/09 10:34:52 PM Accord[13608] kCGErrorIllegalArgument: CGSClearWindowTags: Invalid window 0x0

11/18/09 10:34:52 PM [0x0-0x792792].com.OakTree.Accordance[13608] Wed Nov 18 22:34:52 Carl-Hostetters-MacBook-Air.local Accord[13608] <Error>: kCGErrorIllegalArgument: CGSRemoveWindowFromWindowMovementGroup: Invalid window

 

The actual crashes, which occurred the first time I tried to create some Tool Sets, produced this set of messages:

 

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] An unhandled exception occurred at $92C2FE63 :

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] EAccessViolation : Access violation

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C2FE63

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C2F8C0

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C2FE27

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C309E0

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C300F0

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C2FF4F

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C64B2C

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C3127A

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C300F0

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92C52981

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92DDB81B

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92DE5453

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92DE5657

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92DE5914

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $92

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] DE5ABF

11/18/09 7:53:56 PM [0x0-0x772772].com.OakTree.Accordance[13314] $002E1EE3

11/18/09 7:53:56 PM com.apple.launchd.peruser.502[88] ([0x0-0x772772].com.OakTree.Accordance[13314]) Exited with exit code: 217

11/18/09 7:56:55 PM Accord[13320] Accord(13320,0xa087d500) malloc: *** error for object 0x71d974: incorrect checksum for freed object - object was probably modified after being freed.

*** set a breakpoint in malloc_error_break to debug

11/18/09 7:56:55 PM [0x0-0x775775].com.OakTree.Accordance[13320] Accord(13320,0xa087d500) malloc: *** error for object 0x71d974: incorrect checksum for freed object - object was probably modified after being freed.

11/18/09 7:56:55 PM [0x0-0x775775].com.OakTree.Accordance[13320] *** set a breakpoint in malloc_error_break to debug

11/18/09 7:57:02 PM com.apple.launchd.peruser.502[88] ([0x0-0x775775].com.OakTree.Accordance[13320]) Job appears to have crashed: Illegal instruction

 

Looks like a memory management issue to me.

Link to comment
Share on other sites

Hi Carl,

 

1) I noticed something strange about your scrollbars ... your Accordance dialogs have two sets of scroll arrows. Are you running a third party extention to add this option? Does this corruption happen when you are logged in without it?

 

2) I have not been able to reproduce the corruption.

 

Could you please:

  • quit Accordance
  • delete the Tool Sets preference (from user/Library/Preferences/Accordance Preferences)
  • launch Accordance
  • Add seven simple tools sets (title 1, 2, .., 7) with a few tools in each
  • Describe which set to move to reproduce the corruption

 

 

Mike

Link to comment
Share on other sites

1) The double-arrows at both ends of the scroll bar is achieved with an OS X property setting, not a third-party app. I've been using it for many years, through many versions of OS X, without incident.

 

2) I did as you suggested, removed the Tool Set file completely, started Accordance, and added about 10 tool sets, each with just a few modules, apparently without incident. So I then started populating the tool sets more fully, i.e. the way I wanted them. At one point I was working with a tool set with about 20 modules in it, and decided to delete one of the modules. As soon as I hit the delete button, Accordance instantly crashed. I've copied the system console log of the crash below.

 

Going back in after the crash, the Tool Sets look ok, except that the one I was working on at the time of the crash lost all the modules I'd added (not surprising). But I don't trust the Tool Set file now, so will have to start again, again.

 

Carl

 

 

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] An unhandled exception occurred at $92C2FE63 :

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] EAccessViolation : Access violation

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92C2FE63

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92C2F8C0

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92C2FE27

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92C309E0

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92C300F0

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92C2FF4F

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92D0E4DD

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92D11407

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92D120B0

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92D12355

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92D067A1

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $002D59E2

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $002D5938

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $002D58A6

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $00

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] 2E786E

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92C30E29

11/19/09 9:19:39 AM [0x0-0x2c02c].com.OakTree.Accordance[211] $92C300F0

11/19/09 9:19:39 AM com.apple.launchd.peruser.502[89] ([0x0-0x2c02c].com.OakTree.Accordance[211]) Exited with exit code: 217

Link to comment
Share on other sites

AH HA! Here's how to reproduce the crash:

 

1) Create a new Tool Set

2) Use the shift key to make a continuous selection of a few modules in the lefthand list. Double-click (as I did accidentally) to add all the selected modules _while still maintaining the selection_.

3) Extend the selection a couple more with the shift key, and then hit the "Select->" button.

4) Delete one of the modules added in the first selection+double-click maneuver. Instant crash.

 

Carl

Link to comment
Share on other sites

AH HA! Here's how to reproduce the crash:

 

1) Create a new Tool Set

2) Use the shift key to make a continuous selection of a few modules in the lefthand list. Double-click (as I did accidentally) to add all the selected modules _while still maintaining the selection_.

3) Extend the selection a couple more with the shift key, and then hit the "Select->" button.

4) Delete one of the modules added in the first selection+double-click maneuver. Instant crash.

 

Carl

 

P.S. Just tried this out again. Sometimes I have to delete two or three modules to get the crash, but it DOES crash eventually.

Link to comment
Share on other sites

1) The double-arrows at both ends of the scroll bar is achieved with an OS X property setting, not a third-party app. I've been using it for many years, through many versions of OS X, without incident.

 

I only see two options for scroll arrow placement in the Appearance pref pane (together/At top and bottom). In your pictures you have a set (together) at the top and bottom.

I brought this up because in one of the crashes you listed, Accordance was trying to draw the controls in the dialog.

 

 

P.S. Just tried this out again. Sometimes I have to delete two or three modules to get the crash, but it DOES crash eventually.

 

 

Thank you Carl!! This was helpful because I finally was able to get the crash you reported. I even was able to reproduce the error dialog reported originally. I don't think this is a new problem (to 8.3.x or 8.4).

 

I am sorry for the frustration. We will fix these problems before the next minor release (probably after ETS and SBL meetings).

 

Thank you again for helping me find this obscure bug,

Mike

Link to comment
Share on other sites

I only see two options for scroll arrow placement in the Appearance pref pane (together/At top and bottom). In your pictures you have a set (together) at the top and bottom.

I brought this up because in one of the crashes you listed, Accordance was trying to draw the controls in the dialog.

 

This property isn't exposed in the Settings GUI, but can be set via the command line with:

 

defaults write "Apple Global Domain" AppleScrollBarVariant DoubleBoth

 

 

Thank you Carl!! This was helpful because I finally was able to get the crash you reported. I even was able to reproduce the error dialog reported originally. I don't think this is a new problem (to 8.3.x or 8.4).

 

I am sorry for the frustration. We will fix these problems before the next minor release (probably after ETS and SBL meetings).

 

Thank you again for helping me find this obscure bug,

Mike

 

You're welcome! Glad I could help. Have a great time at ETS/SBL!

 

Carl

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...