Re: How to track down this memory problem?
Re: How to track down this memory problem?
- Subject: Re: How to track down this memory problem?
- From: Adam Knight <email@hidden>
- Date: Sat, 22 Jul 2006 11:37:08 -0500
It was my understanding that after WebKit was a part of the OS that
the HTML features of NSAttributedString were changed to take
advantage of it, so most of that should be resolved at this point.
Now, quite obviously, I'm having a problem with it, so it's possible
more fun is lurking inside, but that was my understanding.
Well, 2.0 will be moving to WebArchives instead of this hack, but 1.x
is out there and needs to be fixed. :\ I'll see if Tidy helps once I
reduce this down to a little app.
--
Adam Knight
If you're not going to stop and appreciate the scenery, you're not
going to
enjoy Myst. The same thing applies on the Mac as well. -- Rand Miller
On Jul 22, 2006, at 7:33 AM, Nir Soffer wrote:
On 22/07/2006, at 09:06, Adam Knight wrote:
My program (Notae) uses Cocoa classes to download a web page and
render it as an attributed string, for one of its features. This
works. However, certain sites cause problems in that when you
switch to the note that has that data the program will crash.
Reliably. With the same backtrace. In Apple's code.
Maybe try to use WebKit instead of a TextView?
I remember that in older os versions, the text system supported
only html 3.2, and I guess that the underlaying code is not well
tested as WebKit. Trying to feed real life html (mostly broken in
so many ways) into the text system is very optimistic.
Another option can be to tidy the html before you feed it into the
text system, this is general practice for processing real life html.
http://tidy.sourceforge.net/
Best Regards,
Nir Soffer
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden