As a new user of TextMate, the only thing that has disappointed me is the incredible slowness of many bundle commands. For instance, if I hit ^⇧D to duplicate the current selection, TextMate beachballs (hangs) for about 15 seconds. This is quite surprising because my machine is fast enough (1.33GHz G4 with 1.2GB RAM) and my files are small (< 200 lines).
If I run top while TextMate is beachballing, I notice that bash is consuming all available CPU cycles. Could there be something wrong with my bash configuration? (I realize that TextMate is probably just running some UNIX commands on top of bash to do the bundle command, but still... 15 seconds of 100% CPU activity just to duplicate a selected line? That can't be right.) Does everyone suffer through this, or only me?
Trevor
P.S. I searched the list archives for this problem, but all I could find were slowness issues related to remote file systems. All the files I'm working with in TextMate are local.
On 09 Jan 2006, at 10:16, Trevor Harmon wrote:
As a new user of TextMate, the only thing that has disappointed me is the incredible slowness of many bundle commands. For instance, if I hit ^⇧D to duplicate the current selection, TextMate beachballs (hangs) for about 15 seconds. This is quite surprising because my machine is fast enough (1.33GHz G4 with 1.2GB RAM) and my files are small (< 200 lines).
If I run top while TextMate is beachballing, I notice that bash is consuming all available CPU cycles. Could there be something wrong with my bash configuration? (I realize that TextMate is probably just running some UNIX commands on top of bash to do the bundle command, but still... 15 seconds of 100% CPU activity just to duplicate a selected line? That can't be right.) Does everyone suffer through this, or only me?
Trevor
P.S. I searched the list archives for this problem, but all I could find were slowness issues related to remote file systems. All the files I'm working with in TextMate are local.
This won't help you much but It's definitely not happening here. (iMac G5 1.8Ghz 1024MB and PowerBook 1.5Ghz 512MB)
-- Fred
On 09/01/2006, at 10:16, Trevor Harmon wrote:
As a new user of TextMate, the only thing that has disappointed me is the incredible slowness of many bundle commands. For instance, if I hit ^⇧D to duplicate the current selection, TextMate beachballs (hangs) for about 15 seconds. This is quite surprising because my machine is fast enough (1.33GHz G4 with 1.2GB RAM) and my files are small (< 200 lines).
This is definately abnormal. While some stuff is slow on my machine also (1GHz G4), with files of that size I haven't experienced that kind of delay.
If I run top while TextMate is beachballing, I notice that bash is consuming all available CPU cycles. Could there be something wrong with my bash configuration? (I realize that TextMate is probably just running some UNIX commands on top of bash to do the bundle command, but still... 15 seconds of 100% CPU activity just to duplicate a selected line? That can't be right.) Does everyone suffer through this, or only me?
The way bash invoked means that (unless you changed something) it will emulate a login-shell and thus source the global profile followed by the first of .bash_profile, .bash_login or .profile in your homedir.
The duplicate line command consists of 'echo' and some bash variable substitutions.
-- Sune.
The way bash invoked means that (unless you changed something) it will emulate a login-shell and thus source the global profile followed by the first of .bash_profile, .bash_login or .profile in your homedir.
The duplicate line command consists of 'echo' and some bash variable substitutions.
I had an issue once where I had some auto-complete things setup for bash that took a long time to load, slowed down all my commands. Allan helped me set it up so it only activated when a interactive shell was used. I'd tell you how he did it but it was on my old computer, not sure I still have the file.
On 09/01/2006, at 15:22, Michael Sheets wrote:
I had an issue once where I had some auto-complete things setup for bash that took a long time to load, slowed down all my commands. Allan helped me set it up so it only activated when a interactive shell was used. I'd tell you how he did it but it was on my old computer, not sure I still have the file.
Coming to think of it, the other day after running the usual build command (cmd-B) in the LaTeX bundle, my system went sluggish.. I found out that a bash process was useing 50% cpu, and the kernel_task was using the rest. Quitting TM didn't help, but killall -9 did, finally :p.
-- Sune.
On Jan 9, 2006, at 3:23 AM, Sune Foldager wrote:
If I run top while TextMate is beachballing, I notice that bash is consuming all available CPU cycles. Could there be something wrong with my bash configuration? (I realize that TextMate is probably just running some UNIX commands on top of bash to do the bundle command, but still... 15 seconds of 100% CPU activity just to duplicate a selected line? That can't be right.) Does everyone suffer through this, or only me?
The way bash invoked means that (unless you changed something) it will emulate a login-shell and thus source the global profile followed by the first of .bash_profile, .bash_login or .profile in your homedir.
Hmm... I have Fink, and it installs an init.sh script that gets called by /etc/profile, so it runs every time a new shell is created. Perhaps that's the source of the problem. Any Fink users out there?
Still, I can't imagine what in init.sh would cause such a slowdown. Normally bash starts up (within Terminal) in a couple of seconds. But I wonder... Fink programs override the default ones, so perhaps I've installed a program that happens to be much slower (due to bugs) than the one it replaces. Just brainstorming here...
Trevor
On Jan 10, 2006, at 1:21 AM, Trevor Harmon wrote:
Hmm... I have Fink, and it installs an init.sh script that gets called by /etc/profile, so it runs every time a new shell is created. Perhaps that's the source of the problem. Any Fink users out there?
I did some more investigating, and it turns out Fink was indeed the source of the problem...sort of. I discovered this in my ~/.profile:
test -r /sw/bin/init.sh && . /sw/bin/init.sh test -r /sw/bin/init.sh && . /sw/bin/init.sh test -r /sw/bin/init.sh && . /sw/bin/init.sh test -r /sw/bin/init.sh && . /sw/bin/init.sh
I have no idea how that command got duplicated across four lines, but I do know that after removing all of them, TextMate is suddenly super- fast! Come to think of it, that command isn't even necessary since there's already an equivalent command in my /etc/profile. Strange... But at least the problem's fixed now!
Trevor
yea... i believe all it does is add the /sw/bin/ stuff to your path if i recall correctly from my brief (very) stint with Fink the other day. You may want to just look in that file and see what exactly it does. if all it does is add /sw/bin to your path, you may want to just do it within your .profile by hand... it'll cause one less process to get spawned each time you startup a shell
Kyle
On 1/10/06, Trevor Harmon trevor@vocaro.com wrote:
On Jan 10, 2006, at 1:21 AM, Trevor Harmon wrote:
Hmm... I have Fink, and it installs an init.sh script that gets called by /etc/profile, so it runs every time a new shell is created. Perhaps that's the source of the problem. Any Fink users out there?
I did some more investigating, and it turns out Fink was indeed the source of the problem...sort of. I discovered this in my ~/.profile:
test -r /sw/bin/init.sh && . /sw/bin/init.sh test -r /sw/bin/init.sh && . /sw/bin/init.sh test -r /sw/bin/init.sh && . /sw/bin/init.sh test -r /sw/bin/init.sh && . /sw/bin/init.sh
I have no idea how that command got duplicated across four lines, but I do know that after removing all of them, TextMate is suddenly super- fast! Come to think of it, that command isn't even necessary since there's already an equivalent command in my /etc/profile. Strange... But at least the problem's fixed now!
Trevor
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
-
Fred B. -
Kyle Swank -
Michael Sheets -
Sune Foldager -
Trevor Harmon