-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashs periodically on Lion #28
Comments
Is there any more context you can add to this, such as what you're doing just prior to the crash? |
It feels very repetitive (at least once day?) but I can't ever quite pin down what I was doing at the time... perhaps trying to close a project or switch to or from Textmate (or to or from one Textmate window)... I did glance at the source... could it be that perhaps cleanupImmediately is not working properly? Thinking specifically of notePreferences and line 154... perhaps on Lion the window or field is deconstructed earlier than you're expecting so it's already gone at the point you're trying to get the value from it? Just a very wild guess... |
I wish it was as straight forward as that... notePreferences isn't anywhere in the call stack so it's not involved. What the stack trace seems to be saying is that an on-screen cell is trying draw but its associated control has been deallocated. As I type this out, I'm beginning to wonder if it's the window's field editor. I'll dig around a bit. |
I can reproduce 100% of the time. |
100% of the time it crashes, every time for me. Fresh install using Lion |
Protocol, can you reproduce? |
I haven't been able to reproduce but I've been running 10.7.2 (pre-release) to verify that one of my open bugs with apple was, in fact, fixed. I'll be revving back to 10.7.1 later today. Trev |
May be a different problem, i'm not able to get a stack trace, it doesn't actually crash, it just beach-balls indefinitely. I'm able to do this every time by following the steps you outlined above 100% of the time. If the app does ever become responsive again (rarely) then clicking on the AckMate window and clicking back to text mate gives me another beach-ball. |
Ping, this is still driving me nuts. Any news? |
Found it. Got distracted by the fact that it didn't happen for me if I used the keyboard to switch back to the main window. Ended up missing a dangling garbage pointer to a delegate during window tear-down - surprised it wasn't a source of crashes on earlier OSX releases really... Checked in the fix, won't be doing a release until I have a chance to review other possible changes (like the stupid UTF8 thing). Trev |
For those looking for a build with this fix: https://github.com/mirell/AckMate/downloads |
this build fixed all of my issues! Couldn't have come at a better time, just started getting a fatal bug with ack in project !! thanks & happy holidays! Schneems On Nov 25, 2011, at 1:47 PM, Eliot Shepard wrote:
|
Another person with same issue:
https://gist.github.com/1184968
Always the same stack track of NSTokenField respondsToSelector:... spoke with Allan Osgard and he said Textmate doesn't even use a NSTokenField and since AckMate did there is a good chance the crash could fall on AckMate's shoulders... can anyone else seeing this problem please jump in here.
My log:
The text was updated successfully, but these errors were encountered: