oc_cuff 2.2.2 Stack-Heap Collision

[Judge17]

Testing the oc_cuffs on a handy seal, I observe something close to 2,000 bytes (not kb, bytes) free at startup. Each pose change consumes something like 600 bytes until stack-heap collision (which she sees and reports to me).

One night, I changed her poses until only a few hundred bytes of free space remained, then stopped. The next day, free space was back to close to 1,800 bytes.

Could be a memory leak, could be lazy garbage collection, could be both.

[NikkiLacrima]

Viewer version and what cuffs are worn ?

If you wait more than 5 seconds between pose changes, do you still get stack heap collisions ?

[Judge17]

I can’t say specifically, but when I was testing, watching the free space decrease, pretty sure I was taking five seconds or more between clicks. Once I realized there was a memory issue, I quit causing stack-heap collisions.

[Judge17]

And I clicked the wrong button; sorry.

[SilkieSabra]

Viewer version is Firestorm current version, the cuffs are Ping's Simplicity cuffs, also current version of OC Addon Cuffs

[Judge17]

As the seal said, and I tried a series of poses, waiting 10 seconds or more between each. Free memory reported, in order: 1,748b, 968b, 796b, 796b, 796b, 796b. It does appear to be stabilizing. I’ll check her later today to see if the amount changes.

[NikkiLacrima]

Try AddOnCuffs PR 7

OpenCollarTeam/AddOnCuffs#7