From 76fb62a226fe2648cd135c126aad3a21574fb142 Mon Sep 17 00:00:00 2001 From: Finnegan's Owner <44065187+pacmano1@users.noreply.github.com> Date: Tue, 29 Sep 2026 11:58:57 -0600 Subject: [PATCH] End custom.vmoptions with a comment so added options keep their newline The startup scripts read .vmoptions files with a shell `while read` loop, which skips a last line that has no trailing newline. An option typed as the last line of conf/custom.vmoptions in an editor that does not add a final newline never reached the JVM, so the engine kept the -Xmx256m from base_includes.vmoptions. The install4j-generated scripts (oieservice, oieserver, oiecommand) use that loop and are not ours to change, so the template now ends with a comment line. Options added above it always end in a newline. If an editor leaves the comment without a newline, the scripts drop the comment, which is harmless. Closes #464 Co-Authored-By: Claude Opus 5.5 Signed-off-by: Finnegan's Owner <44065187+pacmano1@users.noreply.github.com> --- server/conf/custom.vmoptions | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/server/conf/custom.vmoptions b/server/conf/custom.vmoptions index ab1f51fc07..e838de0905 100644 --- a/server/conf/custom.vmoptions +++ b/server/conf/custom.vmoptions @@ -22,3 +22,7 @@ # # Any lines which do not match the special directives above will be passed through directly as # arguments to the java binary. + + + +# Add custom options above this comment.