Recent changes to bugs

#16 Index was outside the bounds of the array

Bradley Peet — Wed, 28 Sep 2016 22:02:31 -0000

I've been battling this thread safety bug and finally figured it out. As you may know, FontData instances are stored in a dictionary and shared globally (via FontDataStock and FontDescriptorStock). FontData.CreateFontSubset() calls over to GlyphDataTable.CompleteGlyphClosure() which calls AddCompositeGlyphs() and that's where the trouble really begins. You wind up with multiple threads changing the FontData instance's Position property simulanteously while trying to read from its buffer. The whole concept of FontData having a "current position" for reading the internal buffer is just asking for trouble in a multi-threaded environment where FontData instances are widely shared.

I've got a fix for this that involves significant (but non-breaking) changes to the FontData class and small changes to GlyphDataTable. If anyone is interested I can elaborate and/or share the code. The PDFSharp version I'm working with is 1.3.2608.

#17 Several ContentWriter bugs

PDFsharp Team — Thu, 06 Nov 2014 16:37:44 -0000

Thank you very much for your feedback.
The fix for 2 will be included in the next release.

We think that your fix for 1 is not the cleanest solution. I think the fix should be made with CArray or CSequence. Can you provide a PDF file and may some (more) code that allows us to replicate the problem?

#13 unbelievable Font size

PDFsharp Team — Thu, 06 Nov 2014 12:51:23 -0000

status: open --> accepted
Group: --> v1.0 (example)

#13 unbelievable Font size

PDFsharp Team — Thu, 06 Nov 2014 12:50:44 -0000

Fix can be found here:
http://forum.pdfsharp.net/viewtopic.php?p=7853#p7853

Fix will be included with the next release.

#17 Several ContentWriter bugs

PDFsharp Team — Wed, 19 Jun 2013 14:21:18 -0000

status: open --> accepted

#17 Several ContentWriter bugs

PDFsharp Team — Wed, 19 Jun 2013 14:16:07 -0000

Thank you for the bug fixes, they are on the list for the next major update.

Re second fix:
It seems that "#.0#########" would sometimes save a byte (but I didn't test it yet).

Several ContentWriter bugs

xiperware — Wed, 19 Jun 2013 05:38:32 -0000

The following code can break a pdf file by changing its content to something invalid.

CSequence content = ContentReader.ReadContent( page );
byte[] data = content.ToContent();
page.Contents.Elements.GetDictionary( 0 ).Stream.Value = data;
doc.Save( outputFile );

1) CArray with multiple CReals are not seperated with spaces

Old: [6.1048 6.1048 ]0 d
New: [6.10486.1048]0 d

(My fix: move the '+ " "' in CInteger and CReal from WriteObject() to ToString())

2) CReal's of sufficient precision are converted to scientific notation

Old: .017701 .089784 .91061 .000031 k
New: 0.017701 0.089784 0.91061 3.1E-05 k

(My fix: add format "0.0#########" to CReal.ToString())

Several ContentWriter bugs

xiperware — Wed, 19 Jun 2013 05:38:32 -0000

Ticket 17 has been modified: Several ContentWriter bugs
Edited By: PDFsharp Team (pdfsharp)
Status updated: u'open' => u'accepted'

#16 Index was outside the bounds of the array

PDFsharp Team — Mon, 13 May 2013 09:23:43 -0000

status: open --> closed
Group: --> v1.0 (example)

#14 Faulty dirty tracking in XSolidBrush Color setter

PDFsharp Team — Mon, 13 May 2013 09:20:39 -0000

status: open --> closed
Group: --> v1.0 (example)