I first noticed this months ago, but I’m finally trying to figure it out.
If I click “Select Bundle Item…” or hit ⌃⌘T, the application will freeze. If I check Activity Monitor, TextMate will just keep consuming more memory until I kill it or the system runs out.
Where should I start troubleshooting?
I’ve uploaded a sample taken while TextMate was hung.
http://cl.ly/text/2u473S2I4240
Thanks.
On 16 Jul 2015, at 4:48, Rob McBroom wrote:
If I click “Select Bundle Item…” or hit ⌃⌘T, the application will freeze. If I check Activity Monitor, TextMate will just keep consuming more memory until I kill it or the system runs out.
Where should I start troubleshooting?
From the sample, it appears TextMate is working on sorting the bundle items based on their menu layout.
So it might be that some bundle has a broken menu structure that causes an infinite loop.
Please try first remove all bundles from ~/Library/Application Support/{Avian,TextMate}
If this makes the chooser work, move back half, repeat until the problematic bundle is found.
If you are able to locate the bundle causing the issue, I would very much like a copy!
On 16 Jul 2015, at 2:45, Allan Odgaard wrote:
So it might be that some bundle has a broken menu structure that causes an infinite loop.
Please try first remove all bundles from ~/Library/Application Support/{Avian,TextMate}
My first thought was a bad bundle so before contacting the list, I quit TextMate, moved those folders to the Desktop, and started it again. It didn’t help.
I just tried it again (even moving them to the Trash) and looking more closely, I still see all the same bundles listed on the Bundles menu, along with their underlying menu structure.
The actual grammars, themes, snippets, etc. *do* appear to be gone, but if the problem is with the menu as you suspect, the fact that those things are hanging around would explain continued problems.
So, how to I force a rebuild of the Bundles menu?
On 16 Jul 2015, at 7:53, Allan Odgaard wrote:
Please keep a backup though! If it’s corrupt (the cause), I would like to get a copy.
You mean if `BundlesIndex.binary` is corrupt? That doesn’t appear to be the case.
I tried removing the most suspicious bundle first: my personal one. Of course that was the one causing the problem.
Before I try to fix it, I’ve made a copy in case you want to reproduce the problem of the infinite loop. http://cl.ly/2t2g0F0L2A3N
Thanks again.
On 16 Jul 2015, at 14:26, Rob McBroom wrote:
I tried removing the most suspicious bundle first: my personal one. Of course that was the one causing the problem.
Before I try to fix it, I’ve made a copy in case you want to reproduce the problem of the infinite loop. http://cl.ly/2t2g0F0L2A3N
Thanks, the issue is with the LDAP/LDIF submenu.
Here there is an item with UUID 656CF73E-AB84-4D9F-82F1-DAB847ABB52D which is the UUID of the bundle itself, so that submenu causes the loop.
I’ll add a check for this in next build (loops in the bundle menu structure).
On 16 Jul 2015, at 10:28, Allan Odgaard wrote:
Thanks, the issue is with the LDAP/LDIF submenu.
Here there is an item with UUID 656CF73E-AB84-4D9F-82F1-DAB847ABB52D which is the UUID of the bundle itself, so that submenu causes the loop.
I’ll add a check for this in next build (loops in the bundle menu structure).
Thanks. I generated a new UUID and fixed it by hand. ⌃⌘T works as expected now.
For what it’s worth, that’s one of the more recent snippets I have (created March 20) and I don’t recall doing anything unusual. I created three others that same day, no doubt following the same steps, and they all turned out fine.
-
Allan Odgaard -
Rob McBroom