#77 exception trouble in nMessage constructor

v0.2.8_betaX
closed-fixed
Manuel Moos
None
4
2005-11-21
2005-05-20
Manuel Moos
No

When a short UDP packet is received and the
exception inside the nMessage constructor is thrown,
there's a memory leak and a fake assertion failure in
debug mode. Plus, the claim_id sent may be
considered part of the message (no exploits possible,
but a bug nontheless).

Discussion

  • Manuel Moos
    Manuel Moos
    2005-05-20

    • summary: Memory leak on exception in nMessage constructor --> exception trouble in nMessage constructor
     
  • Manuel Moos
    Manuel Moos
    2005-05-20

    Logged In: YES
    user_id=34808

    I't not a memory leak after all; the data is held in a tArray
    which will clear itself in the member destructor that's
    automatically called. But the other problems are real.

     
  • Manuel Moos
    Manuel Moos
    2005-08-12

    Logged In: YES
    user_id=34808

    Small and ugly internal problem, postponed the fix to after
    0.2.8.

     
  • Manuel Moos
    Manuel Moos
    2005-08-12

    • priority: 5 --> 4
    • status: open --> open-postponed
     
  • Manuel Moos
    Manuel Moos
    2005-08-22

    • milestone: --> v0.2.8_betaX
     
  • Manuel Moos
    Manuel Moos
    2005-11-06

    Logged In: YES
    user_id=34808

    The claim_id problem is not real, either. It is removed from
    the data that is to be turned into messages. The assertion
    failure is fixed, referenceable objects with refcount zero are
    allowed to delete themselves.

     
  • Manuel Moos
    Manuel Moos
    2005-11-06

    • status: open-postponed --> pending-fixed
     
  • Manuel Moos
    Manuel Moos
    2005-11-06

    • status: pending-fixed --> open-fixed
     
  • Manuel Moos
    Manuel Moos
    2005-11-06

    Logged In: YES
    user_id=34808

    The claim_id problem is not real, either. It is removed from
    the data that is to be turned into messages. The assertion
    failure is fixed, referenceable objects with refcount zero are
    allowed to delete themselves.

     
  • Manuel Moos
    Manuel Moos
    2005-11-06

    • status: open-fixed --> pending-fixed
     
    • status: pending-fixed --> closed-fixed
     
  • Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).