Re: PDFKit and 64-bit bugs
Ken Ferry <[email protected]>
| Newsgroups | gmane.comp.macosx.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Christiaan, It's very good that you filed these bugs. Since these problems are so easy for you to reproduce, you might consider tossing in a demo that exercises the bug. I don't think the repro steps can really be as generic as they seem. For example, one says "Whenever I try to get the attributedString property of a PDFPage object, I get a warning that a deallocated object is autoreleased." Well, Preview is a 64 bit app that uses PDFKit. I just tried calling attributedString in there via gdb, and it seemed to work okay. A bug that is reproducible is fixable. A bug report that is obviously valid and reproducible is easy pickings. :-) -Ken On Sat, Sep 5, 2009 at 3:10 PM, Christiaan Hofman <[email protected]>wrote: > I've finally moved to upgrade a PDFKit app to 64-bits. However, it's giving > me all kinds of crashers which I'm pretty sure are bugs in PDFKit. It seems > that whenever I call -[PDFBorder dashPattern] or -[PDFPage attributedString] > it crashes, and on 10.5.8 also -[PDFView areaOfInterestForMouse:] (though > that seems to originate in -[PDFPage loadTextChars]). I've found some ugly > workarounds for the first two, but the last one remains illusive. > > I wonder whether others on this list had similar problems? And in > particular, whether others know workarounds for these bugs, in particular > the third one? > > Thanks, > Christiaan > > _______________________________________________ > MacOSX-dev mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-dev >