fatal allocation - Githubissues

Masuzu / SarasaBot

A GBF bot for automated raid farming with scriptable behaviour

https://gbtools.azurewebsites.net/SarasaBot/en/Home

27 stars 4 forks source link

fatal allocation #302

Closed tidusZX closed 4 years ago

tidusZX commented 4 years ago

I keep getting this after 1 attack aand the whole bot stops

CorrinKrow commented 4 years ago

recieving the same error, in v 2.11.0

Fatal error 5 Uh oh device or resorce busy:device or resource busy

Fatal eror 7 Uh oh bd allocation

DarkHorse1121 commented 4 years ago

Also faced same issue.

rabbit02178 commented 4 years ago

same issue

smallqp commented 4 years ago

Me too.

Masuzu commented 4 years ago

Quick update on this matter: I can reproduce consistently the case when the "Device or resource busy" errors occur in some contrived cases: the problem is clearly understood this time around. I believe it can only happens in 2 cases currently: casting summons or casting skills

As for the bad allocations this might be a bit trickier but we'll get down to the root cause. I wonder if it only happens for Fatal error 7 messages though.

Masuzu commented 4 years ago

"Fatal error 5" errors and similar ones indicating that a "device or resource is busy" are handled in v2.11.1. As for bad allocation errors, they may still appear. Should you encounter them by some unfortunate event, please report both:

the fatal error code (for instance "Fatal error 5")
the last console log lines <- this is especially important to avoid beating around the bush ... and secondarily ping the Partner role in https://discord.gg/JaNR87n

Your help is extremely appreciated, thank you!