#1139 MT cache cleared on saving or committing translation to memory

[Kos Ivantsov]

When "Automatically fetch translations" is off, and translations are fetched with Ctrl+M for current segment, they show up in the Machine Translation pane as long as no segment is changes or the project is saved.
If any segment (doesn't matter if it has cached MT results or not) is edited and then changed (thus committing the translation to memory), the complete MT cache for the whole project is cleared. The same happens on project save.
It looks like a recent regression, so if this bug is fixed before 5.8/6 is released, it can be changed to closed-fixed right away.

[Hiroshi Miura]

I've implemented a cache clear when Project change event issued. It is a bug fix that previous never release memory to consume it forever, and ultimately OmegaT become dead with Out-Of-Memory.

https://omegat.readthedocs.io/en/latest/22.CoreEvents/

Do we not clear cache without its size?
Current implementation hold 1_000 Least-Recently-Used entries, and when user query next, oldest used entry will be removed.

[Hiroshi Miura]

The event will be issued by project save and modification.
We should handle it only when project become closed.

    enum PROJECT_CHANGE_TYPE {
        CLOSE, COMPILE, CREATE, LOAD, SAVE, MODIFIED
    }

[Hiroshi Miura]

The fix is proposed
https://github.com/omegat-org/omegat/pull/424

[Hiroshi Miura]

The fix is merged into master

[Hiroshi Miura]

released 6.0