[mapguide-trac] #1268: MgNamedCollection cache can become stale and cause crashes by holding refs to deleted objects

[MapGuide Open Source]

#1268: MgNamedCollection cache can become stale and cause crashes by holding refs
to deleted objects
----------------------------+-----------------------------------------------
   Reporter:  tomfukushima  |       Owner:       
       Type:  defect        |      Status:  new  
   Priority:  high          |   Milestone:       
  Component:  General       |     Version:  2.1.0
   Severity:  major         |    Keywords:       
External_id:  1289652.01    |  
----------------------------+-----------------------------------------------
 When more than 10 elements are added to the !MgNamedCollection it will
 switch to using a  std::map for faster lookups.

 Unfortunately, the key used for lookup can be renamed after the std::map
 was created, the key for that element would be invalid and if the renamed
 element is removed, its entry in the map would not be removed (becomes an
 orphan) and thus opens up opportunities for crashes whenever a query comes
 in looking for the same element by name because of a stale object stored
 for the queried element name.

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/1268>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals