> Your comments do make sense. But the glitch lies in the code where it tries
> to format a chunk of text with CTFrameSetter. I doubt it might have been
> trapped into some infinite loop of memory allocation in the implementation
> of
> CTFrameSetterCreateFrame, and that's the reason why it's
Your comments do make sense. But the glitch lies in the code where it tries
to format a chunk of text with CTFrameSetter. I doubt it might have been
trapped into some infinite loop of memory allocation in the implementation
of
CTFrameSetterCreateFrame, and that's the reason why it's allocating a m
Yes, CoreText is our core layout technology, and the Text System is built upon
it.
The difference is that the Text System utilizes the framework as its layout
engine and provides functionalities beyond.
For example, efficiently working with large documents is one of the
higher-level additions
But as I understand, Cocoa Test System, the NSLayoutManager and its
supplementary classes are built upon Core Text. So if Core Text doesn't
work, there's no reason cocoa test would succeedl, right?
DairyKnight
On Thu, Nov 12, 2009 at 2:20 AM, Aki Inoue wrote:
> Hi,
>
> CoreText is designed to
Hi,
CoreText is designed to be a core line layout engine, a building block for
full-fledged text systems like the Cocoa Text System or WebKit.
So, it's not meant for this kind of full document processing.
It's hitting the 4GB memory barrier. I can reproduce the same issue on SL
running in 32b
Hi all,
I'm working with a program utilizing Core Text, but occurred to some strange
problems. When trying to reformat a document
larger than 1MB, the program crashes with the following error msg:
malloc: *** mmap(size=4,294,598,656) failed (error code=12)
*** error: can't allocate region
*** set
