[
https://issues.apache.org/jira/browse/FELIX-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196992#comment-15196992
]
ASF GitHub Bot commented on FELIX-5218:
---------------------------------------
GitHub user CodingFabian opened a pull request:
https://github.com/apache/felix/pull/59
[FELIX-5218] fileinstall: Removed files should no longer be considere…
…d changed.
This is probably a regression from adding the stable checksum mechanism.
All removed files need to be removed from the "changed" hash set, otherwise
they would be seen next iteration again and again be considered as removed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/CodingFabian/felix FELIX-5218
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/felix/pull/59.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #59
----
commit cc1ba9b565256f2a7cf7de0d261127b50ec9ca56
Author: Fabian Lange <lange.fab...@gmail.com>
Date: 2016-03-16T08:12:51Z
[FELIX-5218] fileinstall: Removed files should no longer be considered
changed.
----
> Fileinstall MemoryLeak / Performance degradation in WatcherScanner
> ------------------------------------------------------------------
>
> Key: FELIX-5218
> URL: https://issues.apache.org/jira/browse/FELIX-5218
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Reporter: Fabian Lange
>
> WatcherScanner has a Watcher (called ScannerWatcher :-)) which will fill a
> set with all files that have been changed, so that it then can iterate over
> that.
> however the set will never be cleaned, which leads to the problem that
> removed entries will be "removed" over and over again. ultimately bringing
> the system to a halt because it is busy removing stuff
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
