A number of times in the last week TM2 has crashed (with unsaved work) when I have accidently dragged selected text.
I have NOT yet been able to make a simple replication.
Has anyone else noticed a problem like this?
I have submitted the crash reports to Apple and I DO have "Submit crash reports to MacroMates" turned on. Hopefully this means the reports are getting to Allan and they provide some clues.
I had the same thing happen a few times as well.
Accidental dragging, then crash. Funny, how it only happens when "accidentally" dragging... :)
Never happened when it was intentional.
Thomas
On Mar 3, 2012, at 19:16, Stephen Bannasch wrote:
A number of times in the last week TM2 has crashed (with unsaved work) when I have accidently dragged selected text.
I have NOT yet been able to make a simple replication.
Has anyone else noticed a problem like this?
I have submitted the crash reports to Apple and I DO have "Submit crash reports to MacroMates" turned on. Hopefully this means the reports are getting to Allan and they provide some clues.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
At 7:22 PM +0100 3/3/12, Thomas Krajacic wrote:
I had the same thing happen a few times as well.
Accidental dragging, then crash. Funny, how it only happens when "accidentally" dragging... :)
Never happened when it was intentional.
More information on the crash.
If I move the cursor to a location to start a drag-selection and pause at the beginning the cursor changes from a vertical bar to a selection one char wide.
If I then move the drag-location and mouseup TM2 crashes.
If instead of mouseup I move back to my original mousedown location and move horizontally carefully at just the right spot the the one-char wide gray selection changes back to a vertical bar and I can mouseup without crashing.
I have not been able to reproduce this when just starting TM2 with a single file.
This behavior starts occurring after having used TM2 for a while.
I figured out how to reproduce this issue consistently on my machine:
1. Type something, anything, a few characters to give your cursor some room to move. 2. Find your blinking input cursor, probably at the end of the line 3. Move your mouse directly over the blinking end-line cursor, it has to be pixel-perfect lined up 4. Click and hold, now drag your mouse elsewhere, it should look like it's highlighting 1 char-width blocks where text is present 5. Let go, crash, and profit... or not :D
To prevent crashing:
If you click and drag, and notice that you are highlighting single characters, drag all the way up to the title bar, off the actual text entry area, then let go, that should prevent the crash. It may work if you drag anywhere outside of the text area and let go, not sure.
This has been driving me bat-shit-crazy the last week or so, I don't know exactly when it started happening. The issue was present in an earlier build, but instead of crashing, it would scroll you to the top. Now it crashes.
Let me know if you guys can reproduce the same way I can... curious to know.
Joining in to those that have the problem (reproduceble the same way), here is what I also showed to Allan (in case someone is interested).
VERSION: 9092 This has only been a bug in later releases, as far as i recall, it wasn't a problem for about 4 bug-fix releases ago (the hold option while pressing update).
PROBLEM: Textmate crashes when using the “select first word and drag it around” on an empty selection (just the cursor).
STEPS TO REPRODUCE: · Have the cursor located at a point. · Move the mouse at the EXACT same position as the cursor. · Click, hold and drag around.
There is nothing in the selection, so it looks like you're dragging around the cursor. When you "let go" of the selection (ie drop it), TextMate crashes.
ERROR LOG OUTPUT:
Process: TextMate [80794] Path: /Applications/TextMate.app/Contents/MacOS/TextMate Identifier: com.macromates.TextMate.preview Version: 2.0 (9092) Code Type: X86 (Native) Parent Process: launchd [212]
Date/Time: 2012-03-05 10:26:58.954 +0100 OS Version: Mac OS X 10.7.3 (11D42) Report Version: 9
Interval Since Last Report: 239892 sec Crashes Since Last Report: 10 Per-App Interval Since Last Report: 239834 sec Per-App Crashes Since Last Report: 9 Anonymous UUID: C5AF5022-0830-43EC-BEDB-0C43BE174844
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fffffff4
VM Regions Near 0xfffffff4: --> shared memory 00000000ffff0000-00000000ffff2000 [ 8K] r-x/r-x SM=SHM
Application Specific Information: objc[80794]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 liblayout.dylib 0x00621416 ng::layout_t::end_refresh_cycle(ng::ranges_t const&, CGRect, ng::ranges_t const&) + 170 1 com.macromates.TextMate.OakTextView 0x005d89a8 0x5a8000 + 199080 2 com.macromates.TextMate.OakTextView 0x005caf1c 0x5a8000 + 143132 3 com.apple.AppKit 0x964f7eca NSCoreDragReceiveMessageProc + 1874 4 com.apple.HIServices 0x9a99ee5a CallReceiveMessageCollectionWithMessage + 65 5 com.apple.HIServices 0x9a99ef74 DoMultipartDropMessage + 119 6 com.apple.HIServices 0x9a99f1ba DoDropMessage + 65 7 com.apple.HIServices 0x9a99f791 SendDropMessage + 43 8 com.apple.HIServices 0x9a9a2956 DragInApplication + 705 9 com.apple.HIServices 0x9a9a2c09 CoreDragStartDragging + 535 10 com.apple.AppKit 0x964f8d52 -[NSCoreDragManager _dragUntilMouseUp:accepted:] + 1473 11 com.apple.AppKit 0x964f9e50 -[NSCoreDragManager dragImage:fromWindow:at:offset:event:pasteboard:source:slideBack:] + 1415 12 com.apple.AppKit 0x968539c7 -[NSWindow(NSDrag) dragImage:at:offset:event:pasteboard:source:slideBack:] + 142 13 com.apple.AppKit 0x968531ff -[NSView(NSDrag) dragImage:at:offset:event:pasteboard:source:slideBack:] + 152 14 com.macromates.TextMate.OakTextView 0x005cbf7a 0x5a8000 + 147322 15 com.macromates.TextMate.OakTextView 0x005ccfd8 0x5a8000 + 151512 16 com.apple.AppKit 0x961bcd23 -[NSWindow sendEvent:] + 7659 17 com.apple.AppKit 0x961550e7 -[NSApplication sendEvent:] + 4788 18 com.apple.AppKit 0x960e66d5 -[NSApplication run] + 1007 19 com.apple.AppKit 0x9637a261 NSApplicationMain + 1054 20 com.macromates.TextMate.preview 0x00015239 0x1000 + 82489 21 com.macromates.TextMate.preview 0x00004045 0x1000 + 12357
Evan Villemez wrote:
I figured out how to reproduce this issue consistently on my machine:
- Type something, anything, a few characters to give your cursor some
room to move. 2. Find your blinking input cursor, probably at the end of the line 3. Move your mouse directly over the blinking end-line cursor, it has to be pixel-perfect lined up 4. Click and hold, now drag your mouse elsewhere, it should look like it's highlighting 1 char-width blocks where text is present 5. Let go, crash, and profit... or not :D
To prevent crashing:
If you click and drag, and notice that you are highlighting single characters, drag all the way up to the title bar, off the actual text entry area, then let go, that should prevent the crash. It may work if you drag anywhere outside of the text area and let go, not sure.
This has been driving me bat-shit-crazy the last week or so, I don't know exactly when it started happening. The issue was present in an earlier build, but instead of crashing, it would scroll you to the top. Now it crashes.
Let me know if you guys can reproduce the same way I can... curious to know.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
At 11:52 AM -0800 3/6/12, Evan Villemez wrote:
I figured out how to reproduce this issue consistently on my machine:
- Type something, anything, a few characters to give your cursor some
room to move. 2. Find your blinking input cursor, probably at the end of the line 3. Move your mouse directly over the blinking end-line cursor, it has to be pixel-perfect lined up 4. Click and hold, now drag your mouse elsewhere, it should look like it's highlighting 1 char-width blocks where text is present 5. Let go, crash, and profit... or not :D
To prevent crashing:
If you click and drag, and notice that you are highlighting single characters, drag all the way up to the title bar, off the actual text entry area, then let go, that should prevent the crash. It may work if you drag anywhere outside of the text area and let go, not sure.
This has been driving me bat-shit-crazy the last week or so, I don't know exactly when it started happening. The issue was present in an earlier build, but instead of crashing, it would scroll you to the top. Now it crashes.
Let me know if you guys can reproduce the same way I can... curious to know.
Yes. I can reproduce following your instructions.
I have lost enough work that I find myself avoiding dragging to select in TM2 -- instead I click, move cursor, and shift click to select an area.
On 07/03/2012, at 03.27, Stephen Bannasch wrote:
At 11:52 AM -0800 3/6/12, Evan Villemez wrote:
I figured out how to reproduce this issue consistently on my machine: […]
Thanks, should be fixed in latest test build.
I have lost enough work that I find myself avoiding dragging to select in TM2 -- instead I click, move cursor, and shift click to select an area.
You lost significant amount of work with TM2? It should be quite good at restore your sessions and modified documents after a crash, so I’d be interesting if it has a blind-spot.
At 1:10 PM +0700 3/12/12, Allan Odgaard wrote:
On 07/03/2012, at 03.27, Stephen Bannasch wrote:
At 11:52 AM -0800 3/6/12, Evan Villemez wrote:
I figured out how to reproduce this issue consistently on my machine: []
Thanks, should be fixed in latest test build.
I have lost enough work that I find myself avoiding dragging to select in TM2 -- instead I click, move cursor, and shift click to select an area.
You lost significant amount of work with TM2? It should be quite good at restore your sessions and modified documents after a crash, so I'd be interesting if it has a blind-spot.
Here's a youtube video showing changes to source, then I cause the crash, reopen TM2, changes are gone.
At 10:16 PM +0700 3/12/12, Allan Odgaard wrote:
On 12/03/2012, at 21.26, Stephen Bannasch wrote:
[] Here's a youtube video showing changes to source, then I cause the crash, reopen TM2, changes are gone.
Did you disable "Open documents from last session" in Preferences?
Yes. I had found the behavior annoying.
... but with "Open documents from last session" enabled the changes I had make just before the crash are restored.
At 11:53 AM -0400 3/12/12, Stephen Bannasch wrote:
At 10:16 PM +0700 3/12/12, Allan Odgaard wrote:
On 12/03/2012, at 21.26, Stephen Bannasch wrote:
[] Here's a youtube video showing changes to source, then I cause the crash, reopen TM2, changes are gone.
Did you disable "Open documents from last session" in Preferences?
Yes. I had found the behavior annoying.
... but with "Open documents from last session" enabled the changes I had make just before the crash are restored.
This bug is getting more and more annoying.
The crash happens easily and often.
Thelast several times after the crahs starts -- textmate takes about 10 minutes to actually quit.
Sometimes I'll force quit but the textmate windows stay visible even though textmate doesn't appear to be running anymore.
-
Allan Odgaard -
Evan Villemez -
Stephen Bannasch -
Tehnix -
Thomas Krajacic