the CPU also pegs at 100% most likely due to excessive logging.
nd and ngui communicate via a stdin/out pipe. feels like the pipe isn't actually open at start, until something is written to it.
until the first touchscreen action occurs
actually, it seems to be until the first msg from nd is received.
right after a reboot or the sv service restart, seeing this msg ~~until the first touchscreen action occurs~~:
> error(ngui): commThreadLoopCycle: error.CommReadInvalidTag
the CPU also pegs at 100% most likely due to excessive logging.
`nd` and `ngui` communicate via a stdin/out pipe. feels like the pipe isn't actually open at start, until something is written to it.
> until the first touchscreen action occurs
actually, it seems to be until the first msg from nd is received.
x1ddos
added this to the mvp v1.0 milestone 2 years ago
right after a reboot or the sv service restart, seeing this msg
until the first touchscreen action occurs:the CPU also pegs at 100% most likely due to excessive logging.
ndandnguicommunicate via a stdin/out pipe. feels like the pipe isn't actually open at start, until something is written to it.actually, it seems to be until the first msg from nd is received.
ngui CommReadInvalidTag error on startupto ngui: CommReadInvalidTag error on startup 2 years agocompleted in #23