Random Serialization Errors after Update to .Net 8

We recently updated our software to .Net 8 and have noticed we are now getting random serialization errors when we try to convert to PDF using Aspose.PDF (error below). These are not reproducible on the same file. We are currently running version 24.3.

How can we eliminate these errors?

Serialization error… at #=zryKsIqPIJz1S2_MPOrIzWPbtEgDnU76ZMLHhVlU=.#=zycUtr0U=(#=z0bFPusCvGnzmUfbppdsy13Xp35LSoD4nzJW3f92nUuOa #=zQlS6A95j5ejB, #=z6hEapOXPpKsSmgYjimVml5vgJpIKwaijhQ==& #=zoKSvjUlSCMoV)\r\n at #=zOj0VlyKypTqDkT5xWZloVvmSU8_H9O1DhA==.#=z$yA5coQ=.#=zycUtr0U=(#=z0bFPusCvGnzmUfbppdsy13Xp35LSoD4nzJW3f92nUuOa #=zQlS6A95j5ejB, #=z6hEapOXPpKsSmgYjimVml5vgJpIKwaijhQ==& #=zoKSvjUlSCMoV)\r\n at #=zryKsIqPIJz1S2_MPOrIzWPbtEgDnU76ZMLHhVlU=.#=zycUtr0U=(#=z0bFPusCvGnzmUfbppdsy13Xp35LSoD4nzJW3f92nUuOa #=zQlS6A95j5ejB, #=z6hEapOXPpKsSmgYjimVml5vgJpIKwaijhQ==& #=zoKSvjUlSCMoV)\r\n at #=zFnnh$ePnpQL5BAG$Y5xBvOq5V2bh.#=zuy0zE6g=(#=zYXepG56n$VQE5hFrqonGBprilOgbD4iqeQ== #=zinBxA8s=, Boolean #=zWShqReNVvR8e)\r\n at #=zFnnh$ePnpQL5BAG$Y5xBvOq5V2bh.#=zuy0zE6g=(#=zYXepG56n$VQE5hFrqonGBprilOgbD4iqeQ== #=zinBxA8s=)\r\n at #=zFnnh$ePnpQL5BAG$Y5xBvOq5V2bh.#=zbB1dZl5Num6W(Int32 #=zsLl0pS0=, Int32 #=zcZUZamo=)\r\n at #=zFnnh$ePnpQL5BAG$Y5xBvOq5V2bh.#=zuy0zE6g=(Int32 #=zsLl0pS0=, Int32 #=zcZUZamo=, Boolean #=zWShqReNVvR8e)\r\n at #=zOj0VlyKypTqDkT5xWZloVvmSU8_H9O1DhA==.#=ztWRHUt8=()\r\n at #=zLS$9KpTyQQNMx5cEnWPJcO9Y$Tbi51vfSw==.#=zksAukmwyfcAr()\r\n at #=zLS$9KpTyQQNMx5cEnWPJcO9Y$Tbi51vfSw==.#=z9Cp9qYFWwHaE()\r\n at #=zLS$9KpTyQQNMx5cEnWPJcO9Y$Tbi51vfSw==.#=zAuwD3_s=(Int32 #=zBTPxIo6B34Mj)\r\n at Aspose.Pdf.PageCollection.#=z5VeJ59PAXF1TfZrL_rkEz7A=(Int32 #=zt_0BenU=)\r\n at Aspose.Pdf.Document.#=zDdRx713u$n3PQgOhBRTmw14=()\r\n at Aspose.Pdf.Document.Flatten(FlattenSettings flattenSettings)\r\n at Aspose.Pdf.Document.Flatten()

@bmahlochag

We request you please try using 24.5.1 version of the API and let us know if you still notice this issue. Please share your sample code snippet and file if issue still persists. We will test the scenario in our environment and address it accordingly.