You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the date is changed from the current date to a future date, bad things can happen. This is related to the potential reetrancy issue mentioned (#5 & #8). In my case, I was spawning a new thread on each call, which caused a fork bomb.
I discovered this when I paused a virtual machine for a few days. Unpausing would cause 100% CPU usage and the VM would become unstable. After narrowing down the issue I tried just changing the date to one in the future, and sure enough, the issue popped up again. This could also occur if the system sleeps for a period of time, then wakes up.
The text was updated successfully, but these errors were encountered:
When the date is changed from the current date to a future date, bad things can happen. This is related to the potential reetrancy issue mentioned (#5 & #8). In my case, I was spawning a new thread on each call, which caused a fork bomb.
I discovered this when I paused a virtual machine for a few days. Unpausing would cause 100% CPU usage and the VM would become unstable. After narrowing down the issue I tried just changing the date to one in the future, and sure enough, the issue popped up again. This could also occur if the system sleeps for a period of time, then wakes up.
The text was updated successfully, but these errors were encountered: