Hearthling has not yielded after 35 AI spins

Here’s another one. Is this mining related?

release-537 (x64)
@stonehearth/components/ai/ai_component.lua:566: (3384 Autumn Quess) has not yielded after 10 ai spins. Are they in a bad state? Last abort reason: could not reserve region
stack traceback:
    radiant/modules/common.lua:223: in function 'report_traceback'
    radiant/modules/common.lua:442: in function 'verify'
    stonehearth/components/ai/ai_component.lua:566: in function 
    [C]: in function 'xpcall'
    radiant/modules/common.lua:243: in function 'xpcall'
    stonehearth/components/ai/ai_component.lua:524: in function 'threadmain'
    stonehearth/services/server/threads/thread.lua:249: in function 
    [C]: in function 'xpcall'
    radiant/modules/common.lua:243: in function 'xpcall'
    stonehearth/services/server/threads/thread.lua:246: in function 'f'
    radiant/lib/env.lua:15: in function

From this thread

Yep that’s the mining bug that I fixed.

1 Like

I was just mining a hole!

release-537 (x64)
@stonehearth/components/ai/ai_component.lua:566: (59382 Riley Burlyhands) has not yielded after 10 ai spins. Are they in a bad state? Last abort reason: could not reserve region
stack traceback:
radiant/modules/common.lua:223: in function ‘report_traceback’
radiant/modules/common.lua:442: in function ‘verify’
stonehearth/components/ai/ai_component.lua:566: in function <stonehearth/components/ai/ai_component.lua:524>
[C]: in function ‘xpcall’
radiant/modules/common.lua:243: in function ‘xpcall’
stonehearth/components/ai/ai_component.lua:524: in function ‘_thread_main’
stonehearth/services/server/threads/thread.lua:249: in function <stonehearth/services/server/threads/thread.lua:246>
[C]: in function ‘xpcall’
radiant/modules/common.lua:243: in function ‘xpcall’
stonehearth/services/server/threads/thread.lua:246: in function ‘f’
radiant/lib/env.lua:15: in function <radiant/lib/env.lua:14>

Hey there @Sicario, welcome to the Discourse!

Great news, this bug is already fixed for the next build.

Hey and thanks.

Sorry about creating a duplicate post, I’m still getting used to how this forum works :confused:

No need to apologize! That’s what us mods are here for.

If you are concerned about making duplicate posts (and you shouldn’t worry too much), check out the #support:bug-reports category and do a quick search. If nothing similar comes up, create your new topic. If you find a match, great! Remember, even if search shows no results, there still might be a duplicate. Search can be picky, particularly when dealing with all the formatting of engine errors. The mods read every post posted, so we tend to have a good idea of what exists on the site even when search fails. :smiley.

and i’d like to thank you. i can’t imagine what place this would be without your commitment.

3 Likes

hate to revive a dead topic but alpha 19 brought back this curse

alpha 19 latest unstable branch on steam

No worries! I’ve seen it sporadically as well, but I believe @Albert said it’s not fatal. Will need him to confirm what is going on…

Correct. It’s non-fatal, but will consume more CPU than necessary. It’s probably fallout from building a floor adding multiple blocks where people are standing.

1 Like

Could we please get a in-game screenshot button… I don’t want to crop my image every time.

@Maltavius I think you can use Prt Screen key and a screenshot will be saved in a screenshots folder inside your Stonehearth folder.

2 Likes

Wow, why isn’t this information a part of the "Report a bug information in-game?"
I’ve always done Print Screen, Mspaint, Ctrl-V check if it’s actually what I’m seeing in-game. Crop, Ctrl-C, Paste into forum-post.

Since I have dual monitors I always need to crop, but you are right, it’s actually there in the Screenshot folder…

6 posts were merged into an existing topic: Shepherd doesn’t do anything

release-687 (x64)
@stonehearth/components/ai/ai_component.lua:598: (1810555 Lisy Wester) has not yielded after 10 ai spins. Are they in a bad state? Last abort reasons: <destination (10856651 stonehearth:decoration:firepit_seat) is no longer valid at start. filter description: find lit fire (x10)>
stack traceback:
radiant/modules/common.lua:237: in function 'report_traceback’
radiant/modules/common.lua:456: in function 'verify’
stonehearth/components/ai/ai_component.lua:598: in function <stonehearth/components/ai/ai_component.lua:537>
[C]: in function 'xpcall’
radiant/modules/common.lua:257: in function 'xpcall’
stonehearth/components/ai/ai_component.lua:537: in function '_thread_main’
stonehearth/services/server/threads/thread.lua:273: in function <stonehearth/services/server/threads/thread.lua:270>
[C]: in function 'xpcall’
radiant/modules/common.lua:257: in function 'xpcall’
stonehearth/services/server/threads/thread.lua:270: in function 'f’
radiant/lib/env.lua:15: in function <radiant/lib/env.lua:14>

Welcome to the forum, @Daniel1 :slight_smile:

I’ve merged your report here. This error has nothing to do with the max herthlings. By default, you can only get 20. But if you think your computer can handle more, you can increase the limit in the game Settings (Gameplay tab).

1 Like

as usual your fast to reply to support topics :slight_smile:

release-693 (x64)[M]
@stonehearth/components/ai/ai_component.lua:600: (6453944 Yui Brightwell) has not yielded after 10 ai spins. Are they in a bad state? Last abort reasons: <destination (18644058 stonehearth:decoration:firepit_seat) is no longer valid at start. filter description: find lit fire (x10)>
stack traceback:
radiant/modules/common.lua:237: in function 'report_traceback’
radiant/modules/common.lua:468: in function 'verify’
stonehearth/components/ai/ai_component.lua:600: in function <stonehearth/components/ai/ai_component.lua:539>
[C]: in function 'xpcall’
radiant/modules/common.lua:257: in function 'xpcall’
stonehearth/components/ai/ai_component.lua:539: in function '_thread_main’
stonehearth/services/server/threads/thread.lua:273: in function <stonehearth/services/server/threads/thread.lua:270>
[C]: in function 'xpcall’
radiant/modules/common.lua:257: in function 'xpcall’
stonehearth/services/server/threads/thread.lua:270: in function 'f’
radiant/lib/env.lua:15: in function <radiant/lib/env.lua:14>

Just close that message, as long as you have no problems while playing you can ignore them or send in your log file after each session :slight_smile: hehehehe
There is one error message where you need to hit the F5 button on your keyboard.
But do not worry, the message itselfs tells you to press F5.

1 Like

Oh, but do not think that your post was worthless or something like that.
Even if something has been posted before (bugs, suggestions, etc.) as long as you have tried to search for it, your post was worth the effort.

Better to report something double than to never report anything.

2 Likes