Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-12860

.NET: NullReferenceException when serializing fields of the same type in different order

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.8
    • Fix Version/s: 2.9, 2.8.1
    • Component/s: platforms
    • Labels:

      Description

      .NET NullReferenceException when serializing fields of the same type in different order

      Steps to reproduce:

      • Implement IBinarizable for a type having multiple fields and randomly select subset of the fields in the  IBinarizable.WriteBinary implementation
      • Serialize the type multiple times

      Actual result:

      Eventual NullReferenceException at some iteration of serialization:

      Object reference not set to an instance of an object.  at Apache.Ignite.Core.Impl.Binary.Structure.BinaryStructure.GetFieldId(String fieldName, Byte fieldType, Int32& pathIdx, Int32 actionIdx)   at Apache.Ignite.Core.Impl.Binary.Structure.BinaryStructureTracker.GetFieldId(String fieldName, Byte fieldTypeId)   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteFieldId(String fieldName, Byte fieldTypeId)   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteInt(String fieldName, Int32 val)   at 

        Attachments

          Activity

            People

            • Assignee:
              ptupitsyn Pavel Tupitsyn
              Reporter:
              kukushal Alexey Kukushkin

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 20m
                20m

                  Issue deployment