[
https://issues.apache.org/jira/browse/JENA-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354780#comment-14354780
]
Rob Vesse commented on JENA-898:
--------------------------------
That is a separate issue, while memory mapped files and the on-disk copies are
properly freed on other OSes there is often a small delay between when the JVM
deletes the files and when the OS actually processes the deletions which can
lead to this issue building on any OS when the disk is mostly full
Again there is no real solution to this, we could insert synthetic delays into
the tests but this makes them run substantially slower and doesn't guarantee
that we won't still hit this issue
> Building w/tests on Windows requires a lot of disk space
> --------------------------------------------------------
>
> Key: JENA-898
> URL: https://issues.apache.org/jira/browse/JENA-898
> Project: Apache Jena
> Issue Type: Bug
> Components: TDB
> Affects Versions: Jena 2.12.1, Jena 2.13.0
> Environment: Windows
> Reporter: Stian Soiland-Reyes
>
> mvn clean install
> on Windows, in particular of jena-tdb and jena-jdbc-driver-tdb requires a lot
> of disk space (> 40 GB) as temporary TDB datasets are created per test due to
> the memory mapped files on Windows not being released (JENA-775, JENA-115)
> JENA-897 ensures those files are in target/ when running through Maven, so at
> least they are removed on mvn clean.
> It might be possible to release the ByteBuffers that lock the memory regions
> using System.gc() (which might not help anyway) - but this adds significant
> overhead (~ 1s on my machine) -- perhaps this could be done pr 10 tests in a
> @After if on Windows, as a kind of best-effort clean-up?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
