Find in Project has a memory leak!
Our project contains around 40 MB of source spread out over many many files (We have source trees for Ruby on Rails and Solr in our project). When running any Find in Project operations, memory usage for TM raises to nearly 800 megabytes and then never goes back down.
We've been forced to open sub folders as projects to run our inter-file searches, and it has become a pain.
We've been forced to open sub folders as projects to run our inter-file searches, and it has become a pain.
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Have you let them know about this problem? http://macromates.com/contact
-
Inappropriate?Hey Scott, I'm late to the game here but in case you haven't solved the problem yet, you should know, that you're not alone.
There are a number of tickets and a few choice mailing list posts about the issue. This bug in particular matches your situation pretty closely and even has a comment from Allan (the creator) on the reason that the problem exists.
So, in case you haven't done so yet, here are a few links that talk about possible things that you can do to make your life better:
* Troubleshooting Find in Project (see "Q. How can I improve Find in Project performance?"
* Textmate: remove unnecessary files from Rails project
* Exclude vendor/rails from Textmate projects (an advanced version of the previous)
* Install the Grep in Project bundle which I've heard good things about but haven't yet used myself.
Given the level of complaints about this issue and the general limitations that TextMate has on opening large files, I'm sure that Allan will once again delight us with the next big update.
Take care,
Jay Allen
I’m still in love with TextMate
Loading Profile...




