Free cookie consent management tool by TermsFeed Policy Generator

Changes between Initial Version and Version 1 of Ticket #1268


Ignore:
Timestamp:
11/12/10 12:40:31 (13 years ago)
Author:
svonolfe
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1268 – Description

    initial v1  
    33I was able to trace back the problem to the Run::Initialize method using the CLR profiler and created a patch for that method. The test project contains the patched dll.
    44
    5 Please note if you enable algorithm.StoreAlgorithmInEachRun you can see the memory leak. After applying the patch, if you disable algorithm.StoreAlgorithmInEachRun the memory leak seems to disappear, or at least becomes less severe.
     5Please note if you enable algorithm.!StoreAlgorithmInEachRun you can see the memory leak. After applying the patch, if you disable algorithm.!StoreAlgorithmInEachRun the memory leak seems to disappear, or at least becomes less severe.
    66
    77The problem seems to be related to the recent cloning refactoring.