I'm getting some interesting performance issues that are easy to reproduce in context but difficult to isolate to submit an issue.

The problem seems to be happen when opening a tag in a particular place, causing ST2 to hang for an extended period and use 50% CPU during that time. I'll update this with more information after further testing.

dsarch wrote:I had the same problems today when editing a looooooog ruby file. When i tried to do some search, Sublime just hang and used 100% of cpu.

+1 SublimeTagmatcher seems to have a problem editing large files. ST2 started hanging (after installing couple of plugins) when editing very long files, so I moved my 'Packages' folder, restarted ST2 (simulating a fresh install) and then I started dropping each plugin one after the other (editing a long css file each time i restarted ST2), every thing was fine until I dropped in the SublimeTagmatcher plugin, ST2 started hanging when editing the long file (using almost 100% of cpu).

Yes, I have found that html and css files of only a few hundred lines are having issues. However, some tags don't cause the hangups while others do. I mentioned it was hard to pinpoint exactly what and where the problem lies, as well as how to reproduce it reliably between different files.

As others said before this is a really cool and usefull plugin, and after testing it I have the same problem: With large files it relentizes a lot the editor. I think in files with more than 100 lines aprox. it starts to be really slowly. I don't know if it will be solved in future versions or if it's not possible.

Anyway, one possible 'fast' solution:

- It's possible to have something like an 'extensions blacklist' where put some extension files where don't execute the plugin? It would be really nice, because in my case I have really long css files but smaller templates files. And where I find really usefull this plugin is with the templates files.