I can also reproduce this issue with my trackpad. So, this does not look like it's a hardware issue, or a problem with a specific input device.
I think I've figured out what's going on.
If my mouse is on the extreme right side of the screen, moving right, and I close my inventory, my view snaps to the left. If my mouse is on the left side of the screen, moving left, and I close my inventory, my view snaps to the right.
I think that when the game changes the cursor settings to make the cursor disappear and have mouse movement change where the player looks, the mouse snaps back to the center of the screen, and is hidden. This snap back to the center of the screen is interpreted as mouse input changing where the player is facing.
I've experienced this bug.
I'm currently on MacOS 14.5 on an M1 Mac. I've experienced this on various versions since 1.19 through to the current 1.20.6.
This bug is hard to reproduce, as it happens intermittently. I haven't been able to figure out any rhyme or reason as to when this will or will not happen.
I provided a chart showing CPU usage while the server is idle. What kind of information do you need?
Affects 1.14.4. CPU pegged at 100%.
Linode instance
2 CPUs
4 GB RAM
Debian 9
Not fixed in 1.14.4-pre6
Loaded up 1.14.4-pre6 with a brand new world, and no one logged in. The blip down from 100 is where I stopped the previous version and switched over to 1.14.4-pre6. The CPU jumped back up to 100%. 1.13 idled at or below 20%.
Environment:
Linode Instance
2 CPUs, 4 GB RAM
Debian 9
Affects 1.14.2
No users logged in, CPU pegged at 100%.
This also affects the launcher on MacOS.
Still a problem in 1.14.1
Affects 1.14.1-prerelease-2
Was fighting drowned in some ocean ruins when my server crashed. Restarted the server, and captured this debug session fighting the drowned.
Something else I noticed with this crash, the server exits with exit code 0. I have a bash script which uses the exit code to detect crashes and automatically restart the server. My script failed to restart the server when this crash happened.
Is this expected behavior? If not, should I open a separate bug?
Loaded up a brand new world in 1.14.1 pre-release 1 and began loading chunks. I was able to outrun chunk loading in a boat, but the server seemed to be fairly stable. I jumped into creative and started flying in a straight line, and chunk loading could not keep up. I began getting really bad rubber banding. I landed and stopped moving and later the server crashed because a single tick took over 60 seconds.
Attached file is a debug session from flying in a straight line into ungenerated chunks.
Seeing similarly high idle CPU usage on 1.14.1 pre-release 1.
I'm also seeing this issue with 1.14. I'm seeing the issue on a Linode instance running Debian 9 with 1 CPU and 2 GB RAM. I don't have servers metrics as detailed as in the description of this post, but I'm also seeing 100% CPU utilization when no players are on the server. CPU utilization was about 5% when running 1.13.1.
I'm experiencing this bug on 1.13. It's much more severe than when I reported it. In some locations, items thrown on the ground from inventory turn invisible roughly 50% of the time.
I've tested under Windows 10 and OS X Sierra. The bug happens for me under Windows 10, but not OS X.
In my testing, this seems to be unrelated to teleporting or creative flying. Fireworks fail to work in the first world loaded after starting the game. If you close the world and open any other world, fireworks work correctly. You can trigger the bug again if you exit the game, restart the game, and load a single player world.
I triggered the bug when throwing a stack of string on the ground from my inventory. When I logged back in to the server after crashing the game, the string was visible on the ground in front of me.
Crash report attached. Please let me know if there's any other information you need.
This is happening to me on a server. Do I need to create a crash report from my client, or from my server?
Confirming this on 1.21. It seems to happen consistently on hardcore worlds.