High Memory Usage about validator HOT 1 CLOSED

Well, memory usage of the daemon itself should be very little (few megabytes). Depending on the documents and the scenarios you use, memory consumption can be high. E.g. xrechnung visualisation can lead to high memory consumption under certain circumstances (see issue 73).

The attached log just shows some warnings from jaxb, which is using some reflection operation which won't be allowed in future java version. For next release, we will upgrade the jaxb version and the messages will disappear.

To better investigate whether you we have an issue here, we need more information. What is memory consumption after startup? When is the daemon killed? What was the current action (validating xrechnung document?), when the daemon got killed? Which java version is used? Which jar is used? etc. etc.

from validator.