You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test used the CmvmiLongSignalMemorySnapshot dump codes to analyse if there
were leaks of LongSignalMemory if a transaction failed. (Lack of cleanup...?)
The amount of such free LongSignalMemory were stored in an array of snapshots,
then later analyzed and require's triggered in Cmvmi::execDUMP_STATE_ORD()
if leaks were belived to be found.
That code had two flaws:
1) When analyzing the snapshots we skipped over every 2'nd snapshot,
thus possibly missing some 'increases' and 'decreases' which were counted.
2) In case the snapshot array could not hold all the snapshots being taken
it wrapped around, writing over the first ones.
Patch fixes:
- All snapshots between 'start' and 'stop' is now analyzed.
- Size of the snapshot array is increased from 32 to 256 element.
( Note that 'testFK -n TransError' takes 50 snapshots with default args).
- Removed the wrap around and instead write a warning to the log if
snapshot array size is exceeded. (-> Code also simplified)
Change-Id: I377e35b72e8d694646ed5a9e949c7c7dea981cd4
0 commit comments