Description Robert Kiss 2013-03-08 04:33:50 EST

The MarkerJob hold a list with all the tasks that it have to perform. In the case of a long running job that already acquired a look on the workspace, the list cannot be processed because the MarkerJob does not run.

Unfortunately, the list grows so much that in the end the memory can be exhausted. We saw consumption of hundreds of MB only on that list.

A possible way to decrease the memory allocation would be to eliminate the task that doesn't make sense.

For example, if for file A the current content of the list is:
- DeleteMarker(TYPE_1)
- CreateMarker(TYPE_1)

a call to DeleteMarker(TYPE_1) shall lead to a list of
- DeleteMarker(TYPE_1)

and not to a list of
- DeleteMarker(TYPE_1)
- CreateMarker(TYPE_1)
- DeleteMarker(TYPE_1)

We should not see more then one delete marker per file per type in the list. And in front of such a delete marker there shall not be any create marker for that type and file.

There might be possible to remove some calls to MarkerJob, of course, but currently I didn't make such an analysis.