View Issue Details

IDProjectCategoryView StatusLast Update
0024834RunnerSpinePublic2019-05-14 08:42
ReporterBrandon GoinsAssigned ToRussell Kay 
PriorityMediumSeverityC - GeneralReproducibility100%
Status ClosedResolutionFixed 
PlatformWindowsOS OS Version
Product Version2.1.4 
Target Version2.2.0Fixed in Version2.2.0 
Summary0024834: Spine: Memory leak in skeleton_bone_state_get()
DescriptionIf data exists in a ds_map, skeleton_bone_state_get() does NOT replace it but appears to add to it, although the size of the ds_map does not increase the memory used by it does. Reading from this ds_map will always return the FIRST data written to it, and newer data is inaccessible.

Working around this requires ds_map_clear() to be used, which can be extremely slow when working with large numbers of spine objects and has more of an impact than actual drawing in most cases.
Additional InformationOriginal helpdesk ticket:
1.4 Found In1.4.1763
2.x Runtime Found In
2.x Runtime Verified In9.9.1.1437


Russell Kay

2018-06-14 22:16

Manager   ~0060342

Fixed in gitlab


2018-08-13 11:01

Adminstrator   ~0061172

Is in 1.4.9999.


2018-09-04 14:01

Adminstrator   ~0061487

Is now in 2.2.0.