Re: Strategies for tracking a tricky (typing) slowdown/lag bug
Re: Strategies for tracking a tricky (typing) slowdown/lag bug
- Subject: Re: Strategies for tracking a tricky (typing) slowdown/lag bug
- From: Rick Genter <email@hidden>
- Date: Wed, 23 Sep 2009 07:58:21 -0700
On Sep 23, 2009, at 6:55 AM, Keith Blount wrote:
Hi,
Again, many thanks for the help, I really appreciate it.
To answer Rick's question first - the lag only occurs after typing
for a while, yes (about 1,000 - 2,000 words). It doesn't happen if
you just paste text in, or in documents that have only just been
opened but already contain thousands of words of text.
The reason I asked this is that I suspect (like Jens) that it's not a
memory problem per se. I'm very new to Cocoa, but I've had problems
like this in the past with other frameworks. Typing often ends up
generating events that get logged with some sort of undo manager.
Usually consecutive typing events get coalesced into a single event,
but perhaps in your case something has broken that is preventing this
and the undo manager is having to deal with thousands and thousands of
events, thus slowing it down. When you quit and restart then obviously
the undo manager is starting from a clean slate.
Does your application have any sort of "save" functionality and does
it hook up to the undo system? I'm wondering if you see a performance
improvement after a save without quitting.
--
Rick Genter
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden