Aaron Wood
- woody77
- woody77
- America/Los_Angeles
- Yes
- No
MC-148208
MCL-14482
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
Aaron Wood, could you create a new ticket about that then (if we don't have one already)?
Aaron WoodAaron Wood, could you create a new ticket about that then (if we don't have one already)?
Further, I just caught two villagers using the same jobsite. I broke it while they were doing so, and both immediately lost their professions. But only one claimed it when I re-placed it.
The villagers who lost their trades were ones I hadn't traded with. Except for one villager where I think I traded with them once, but they were still novices (traded for a mending book).
But villagers shouldn't be resetting/losing trades at all when their jobsite blocks aren't being broken. There's a valid path from anywhere in the village to their jobsite.
I'm still seeing this in 1.15.2. If I replace the fences with 2-block high walls of dirt, the problem goes away, but the bees keep trying to pathfind through the fences to get back to their nest/hive.
I usually see this during the Mojang loading screen (now red, with the progress bar). The screen swiches to full-screen, and then crashes during the mojang splash/loading screen. Sometimes almost immediately, sometimes around halfway through the progress bar, rarely towards the end of the progress bar.
My suspicion is that it's related to MacOS switching from the integrated (Intel) gpu, and the on-board, discreet (AMD) gpu. I don't see this issue much, if at all, when using my 4K external monitor (which causes MacOS to already be using the AMD gpu.
I've found a workaround, of sorts, but it's a manual (pita) process:
This switches the laptop to always run on the discrete graphics, which seems to stop the problem from happening. But, if you don't turn it back off when doing with Minecraft, you're going to have terrible battery life when not playing.
Still seeing this with 1.16.4.
Still seeing this with 1.16.4. And I've confirmed that this is an integrated->discreet graphics (a GPU change) happening too late in the loading of the game (the game itself, not the launcher).
I can work around the issue by any of:
Possible fixes would be for the launcher itself to load the big GPU, or for the packaged JVM to trigger the switch to the big GPU.
@markderickson - No, these are different issues, in different applications.
MCL-11621is a crash in the launcher, whereas this issue here is a crash in the jvm running Minecraft itself. (this is evident in the crash reports):This issue:
MCL-11621:OTOH, I haven't been seeing this with 1.17.x, and haven't had time with 1.18 when running without an external monitor (which uses the always uses the discrete GPU, so won't trigger this issue).