I'm trying to use Textmate2 with a big php project. I have made a huge commit in the git repository and while processing the commit Textmate starts to hang bringing the cpu at 80% and memory up to 1.25GB. Looking at the Console this is what I've found
30/01/2012 16:28:23 TextMate[24252] TextMate(24252,0xa059f540) malloc: *** mmap(size=872415232) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug 30/01/2012 16:28:23 [0x0-0x1e91e9].com.macromates.TextMate.preview[24252] TextMate(24252,0xa059f540) malloc: *** mmap(size=872415232) failed (error code=12) 30/01/2012 16:28:23 [0x0-0x1e91e9].com.macromates.TextMate.preview[24252] *** error: can't allocate region 30/01/2012 16:28:23 [0x0-0x1e91e9].com.macromates.TextMate.preview[24252] *** set a breakpoint in malloc_error_break to debug 30/01/2012 16:28:23 TextMate[24252] Attempt to allocate 872415232 bytes for NS/CFData failed 30/01/2012 16:29:15 fseventsd[56] SLOWDOWN: client 0x10082ca00 (pid 24252) sleeping due to too many errors (num usleeps 23) 30/01/2012 16:31:43 fseventsd[56] SLOWDOWN: client 0x10082ca00 (pid 24252) sleeping due to too many errors (num usleeps 35) 30/01/2012 16:34:30 fseventsd[56] SLOWDOWN: client 0x10082ca00 (pid 24252) sleeping due to too many errors (num usleeps 47) 30/01/2012 16:36:35 fseventsd[56] SLOWDOWN: client 0x10082ca00 (pid 24252) sleeping due to too many errors (num usleeps 59)
I have Textmate2 Version 2.0 (9005) installed.
Patrick Polloni
On 30/01/2012, at 23.58, Patrick Polloni wrote:
I'm trying to use Textmate2 with a big php project. I have made a huge commit in the git repository and while processing the commit Textmate starts to hang bringing the cpu at 80% and memory up to 1.25GB. Looking at the Console this is what I've found […]
The Git bundle produces a HTML diff of your commit shown with WebKit.
My guess is that this HTML file simply becomes too big and that’s why TextMate (WebKit) hits the memory celling for what a 32 bit process is allowed to allocate.
The Git bundle tends to be fairly clever about timeouts when generating HTML for various commands, but I guess not in this case.
On 31 Jan 2012, at 08:22, Allan Odgaard wrote:
On 30/01/2012, at 23.58, Patrick Polloni wrote:
I'm trying to use Textmate2 with a big php project. I have made a huge commit in the git repository and while processing the commit Textmate starts to hang bringing the cpu at 80% and memory up to 1.25GB. Looking at the Console this is what I've found […]
The Git bundle produces a HTML diff of your commit shown with WebKit.
My guess is that this HTML file simply becomes too big and that’s why TextMate (WebKit) hits the memory celling for what a 32 bit process is allowed to allocate.
The Git bundle tends to be fairly clever about timeouts when generating HTML for various commands, but I guess not in this case.
I had the same thought. The problem seems to come out when the git bundle try to print in the "HTML output". The point is that there isn't a way to understand if the commit is already completed. Force quitting Textmate could bring to a messy situation. This wasn't the first time I got this problem. After quitting Textmate I still find some file not committed, so it seems that is better to avoid too huge commits.
-
Allan Odgaard -
Patrick Polloni