Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thread Region Scheduler Thread #0 failed main thread check: Accessing entity state off owning region's thread java.lang.Throwable: null #7261

Closed
MrSugar08 opened this issue Feb 18, 2024 · 0 comments · Fixed by #7262
Assignees
Milestone

Comments

@MrSugar08
Copy link

What steps will reproduce the problem?

Just use 1.20.4 folia and start you're server

What is the expected output?

[14:45:07] [Region Scheduler Thread #0/ERROR]: Thread Region Scheduler Thread #0 failed main thread check: Accessing entity state off owning region's thread
java.lang.Throwable: null
at io.papermc.paper.util.TickThread.ensureTickThread(TickThread.java:78) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at org.bukkit.craftbukkit.v1_20_R3.entity.CraftCreeper.getHandle(CraftCreeper.java:91) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at org.bukkit.craftbukkit.v1_20_R3.entity.CraftCreeper.getHandle(CraftCreeper.java:8) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at org.bukkit.craftbukkit.v1_20_R3.entity.CraftEntity.isInWorld(CraftEntity.java:939) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at org.bukkit.craftbukkit.v1_20_R3.entity.CraftEntity.isValid(CraftEntity.java:393) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at org.bukkit.craftbukkit.v1_20_R3.CraftRegionAccessor.lambda$getLivingEntities$2(CraftRegionAccessor.java:321) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at java.lang.Iterable.forEach(Iterable.java:75) ~[?:?]
at org.bukkit.craftbukkit.v1_20_R3.CraftRegionAccessor.getLivingEntities(CraftRegionAccessor.java:317) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at com.palmergames.bukkit.towny.tasks.MobRemovalTimerTask.run(MobRemovalTimerTask.java:96) ~[?:?]
at com.palmergames.bukkit.towny.scheduling.impl.FoliaTaskScheduler.lambda$runRepeating$6(FoliaTaskScheduler.java:87) ~[?:?]
at io.papermc.paper.threadedregions.scheduler.FoliaGlobalRegionScheduler$GlobalScheduledTask.run(FoliaGlobalRegionScheduler.java:179) ~[luminol-1.20.4.jar:?]
at io.papermc.paper.threadedregions.scheduler.FoliaGlobalRegionScheduler.tick(FoliaGlobalRegionScheduler.java:37) ~[luminol-1.20.4.jar:?]
at io.papermc.paper.threadedregions.RegionizedServer.globalTick(RegionizedServer.java:293) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at io.papermc.paper.threadedregions.RegionizedServer$GlobalTickTickHandle.tickRegion(RegionizedServer.java:148) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at io.papermc.paper.threadedregions.TickRegionScheduler$RegionScheduleHandle.runTick(TickRegionScheduler.java:404) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at ca.spottedleaf.concurrentutil.scheduler.SchedulerThreadPool$TickThreadRunner.run(SchedulerThreadPool.java:525) ~[luminol-1.20.4.jar:git-Luminol-"fed8624"]
at java.lang.Thread.run(Thread.java:833) ~[?:?]

Towny version

0.100.1.14

Server version

Folia 1.20.4

Please use Pastebin.com to link the following files

https://hastebin.skyra.pw/tuxowejogi.less latest.log

@MrSugar08 MrSugar08 added the bug label Feb 18, 2024
@LlmDl LlmDl added this to the 0.100.2.0 milestone Feb 18, 2024
LlmDl added a commit that referenced this issue Feb 19, 2024
Warrior with PR #7267.
  - Fix mob removal on folia, courtesy of Warrior with PR #7262.
    - Closes #7261, #7221, #7202, #7253.
  - Make our custom registered commands identifiable, courtesy of
Warrior with PR #7263.
  - Move using_economy to the eco section of the config, courtesy of
Warrior with PR #7265.
  - Automatic config edit:
    - plugin.interfacing.using_economy moves to economy.using_economy
  - Remove uuid percentage tracking, courtesy of Warrior with PR #7266.
  - Make PlotClaim a runnable, courtesy of Warrior with PR #7268.
  - Reorganize test directory layout, courtesy of Warrior with PR #7269.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants