Ron Hunsinger

I found my problem. I recently added a villager trading hall to my base. Wandering traders used to spawn there, but they don't seem to like spawning near a trading hall. When I started hanging out far from my base, they started wandering in again.

No wandering traders have spawned near me for at least 200 minecraft days. Vanilla world in an area where they have spawned frequently in the past. doMobSpawning and doTraderSpawning are both true. I check every 5 real-world minutes with /data get entity @e[type=minecraft:wandering_trader,limit=1] Pos, but it always says "No entity was found". If I summon a wandering trader in, that command finds it, but I don't want to trade with it because that would be cheating, so I kill it.

Still a problem with Launcher version 933(1) under macOS 10.13.6 High Sierra.

The problem seems not to occur after short game sessions. (Under an hour? But who plays Minecraft for under an hour?)

Specifically, the problem is that if you launch the game, play long enough, and then quit, the game itself (java) quits, but the launcher ("Minecraft Launcher" in Activity Monitor, but its real name seems to be "launcher") continues to run. If you try to run it again by clicking on its Dock icon, the OS sees that it's still running and sends it an 'open' event, without bouncing the dock icon. The launcher is not accepting Apple events, so it is now classified as "Application not responding". You can't simply quit the launcher, because it won't accept the 'quit' Apple event either. You have to force quit it, either in Activity Monitor, or by issuing the command 'killall launcher' in Terminal.

This happens to me too. (macOS), Activity Monitor shows that the Launcher continues to run and consumes CPU time even after the main app launches. It stops being responsive when the main app quits, so trying to launch again doesn't work. The remedy I'm using is tor force-quit the launcher thru Activity Monitor, but I have to do that each and every time (after the first launch).

Since when is this intended behavior? I certainly hasn't been in the past. Was it an intentional change? In which version? Why?

Crashes are hard to reproduce, but this particular one has bitten me so often that I've learned to always Quit to Title before interacting with a furnace, especially if I've invested a lot of work since the last save. The crash happens most often when you do multiple interactions with a furnace at one time. (Example: put something in either input bin; change your mind and take it back out; switch to the other bin; put something in; switch back to the first bin; put something in; etc., all without closing the furnace.) But sometimes the crash happens on the first tap, even if all you're doing is removing the product.