[TxMt] Re: A few recent crashes

[Allan Odgaard]

On 22 Apr 2020, at 14:20, Alexander Bohn wrote:

> Hi, I just updated to 2.0.8, and there are a few bugs:
>
> • Running a Python script with ⌘R hangs, producing no output in 
> the HTML
> output window […]
> • Starting up immediately after updating from TextMate 2.0.6 reset 
> the
> theme of every open code window to plain black-and-white […]

I think both of these issues could be caused by a corrupted bundle 
index.

Try quit TextMate, delete this file, and see if ⌘R works again:

	~/Library/Caches/com.macromates.TextMate/BundlesIndex.binary

> • There have been a number of odd hard-crashes – the “Submit 
> Crash Log”
> dialog would come up, saying that TextMate crashed

The crash points to `__CFSocketManager` (system code), I have received a 
similar crash from another client, although that one I have seen before 
(but it’s rare).

Nonetheless, as it appears there might be an issue related to using 
`CFSocket`, I have switched to using a dispatch source instead, as 
that’s anyway a more modern (and thus nicer) API.

Please try 2.0.9 available by holding down option (⌥) when selecting 
TextMate → Check for Update.

> […] in some cases a part of the UI
> would prove to have been rendered unresponsive; in any case a 
> force-quit
> was always necessary.

I have run into this myself, since upgrading to 10.15, it’s when Apple 
throws up dialogs during startup, it can end in a “nested run-loop” 
state where the outer run-loop gets no events, but is blocking the UI 
(waiting for the user to respond to the dialog.

It’s a little tricky to work around with the current code, but I’m 
working on a major overhaul of this and more.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macromates.com/textmate/attachments/20200422/a74a6dc1/attachment.html>