Error in service log reader closing

[DasBabyPixel]

Stacktrace

[17.04 01:37:23.819] ERROR: Unable to read out/err stream of service lobby-1:0c9a8833-9156-4652-9070-85676387b63b
java.lang.NullPointerException: Cannot invoke "java.io.Reader.close()" because "this.reader" is null
    syncat eu.cloudnetservice.node.impl.service.defaults.log.NonBlockingLineReader.close(NonBlockingLineReader.java:185)
        at eu.cloudnetservice.node.impl.service.defaults.log.ProcessServiceLogCache.stop(ProcessServiceLogCache.java:63)
        at eu.cloudnetservice.node.impl.service.defaults.log.ProcessServiceLogCache.readProcessOutputContent(ProcessServiceLogCache.java:99)
        at eu.cloudnetservice.node.impl.service.defaults.log.ProcessServiceLogReadScheduler$ProcessServiceLogReadTask.run(ProcessServiceLogReadScheduler.java:84)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:545)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:369)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:310)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
        at java.base/java.lang.Thread.run(Thread.java:1474)

Actions to reproduce

Can't reproduce, seems like a race condition.
Happened exactly as the service was done stopping, might be coincidence but I don't think so.
My guess is the console reader thread detected that the service is dead. Then it tried to stop/close the cache reader and the JVMService
stopService call raced, since they both call ProcessServiceLogCache#stop and run on different threads

CloudNet version

[17.04 01:43:05.605] INFO :
[17.04 01:43:05.607] INFO : CloudNet Blizzard 4.0.0-RC17-SNAPSHOT 4b3e489
[17.04 01:43:05.608] INFO : Discord: https://discord.cloudnetservice.eu/
[17.04 01:43:05.609] INFO :
[17.04 01:43:05.609] INFO : ClusterId: cff1795a--4230--59d7342463c3
[17.04 01:43:05.610] INFO : NodeId: Node-1
[17.04 01:43:05.611] INFO : Head-NodeId: Node-1
[17.04 01:43:05.612] INFO : CPU usage: (P/S) 5.04/45.34/100%
[17.04 01:43:05.613] INFO : Node services memory allocation (U/R/M): 2524/2524/10000 MB
[17.04 01:43:05.614] INFO : Threads: 49
[17.04 01:43:05.614] INFO : Heap usage: 59/256MB
[17.04 01:43:05.615] INFO : JVM: Eclipse Adoptium 25 (OpenJDK 64-Bit Server VM 25.0.2+10-LTS)
[17.04 01:43:05.616] INFO : Update Repo: CloudNetService/launchermeta, Update Branch: beta (development mode)
[17.04 01:43:05.616] INFO :

Other

No response

Issue uniqueness

• Yes, this issue is unique. There are no similar issues.