Lately TM occasionally crashes on me (once every few days), relevant info:
Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 0 Crashed: 0 com.macromates.textmate 0x0008dabc -[OakTextView (StyleSheet) graphPathForCaretWait:] + 22 1 com.macromates.textmate 0x00089bc1 -[OakTextView (StyleSheet) stylesForCaretWait:] + 35 2 com.macromates.textmate 0x00089bfc -[OakTextView (StyleSheet) stylesForCaret] + 34 3 com.macromates.textmate 0x0001dcec -[OakTextView (ExecuteCommand) environmentVariables] + 60 4 com.macromates.textmate 0x000c5a5c -[NSObject(RunCommand) allEnvironmentVariables] + 592 5 com.macromates.textmate 0x000c5f3a -[NSObject(RunCommand) executeShellCommand:input:variables:returnCode:async:] + 60 6 com.macromates.textmate 0x000c5e36 -[NSObject(RunCommand) executeShellCommand:input:variables:returnCode:] + 62 7 com.macromates.textmate 0x0001ec48 -[OakTextView (ExecuteCommand) executeCommandWithOptions:] + 612 8 com.macromates.textmate 0x0006f03c -[OakTextView performSelector:withObject:] + 450 9 com.macromates.textmate 0x00025fe9 -[OakMacroContinuation delayedExecuteBundleItem:] + 93 10 com.apple.Foundation 0x9280b03b __NSFireDelayedPerform + 403 11 com.apple.CoreFoundation 0x9082d7e2 CFRunLoopRunSpecific + 3341 12 com.apple.CoreFoundation 0x9082cace CFRunLoopRunInMode + 61
Seems to happen when activating/deactivating windows.
On 04/10/2007, at 19:06, Gerd Knops wrote:
Lately TM occasionally crashes on me (once every few days), relevant info: [...]
From that stack trace, what happens here is that a macro is executed, that is triggering a command that needs the document to be saved, but which the document is not.
This will cause the macro to be temporarily halted, while saving of the document takes place (popping up necessary file requesters / warning dialogs, etc.) -- after that, the macro is resumed.
It is after resuming, and querying the scope info in the document, that the crash happens. My guess would be something like maybe the document managed to disappear while the macro was stalled, so it is querying now free’d memory -- but not really sure, seems there is too much activity (in the stack trace) in the OakTextView object, for the object to have gone (i.e. it would normally crash sooner, if the object had been free’d).
Does any of that help maybe get closer to the actual problem causing this? I do believe you have an ⌘S-overlaod, so very likely it is somehow related to that.