Fix fatal error: evacuation not done in time problem
Encounter one of the strangest error messages in Go today regarding evacuation. Now, what the heck "evacuation" has to do with programming language ? Apparently it has something to do with locks.
This error message :
"fatal error: evacuation not done in time"
is caused by accessing a map from multiple go-routines and ....map is not thread-safe.
Solution :
Check if the RLock or Lock is in proper place. Might need some fine tuning through trial and error.
p/s : This solution is applicable to the error message fatal error: bad state as well.
By Adam Ng
IF you gain some knowledge or the information here solved your programming problem. Please consider donating to the less fortunate or some charities that you like. Apart from donation, planting trees, volunteering or reducing your carbon footprint will be great too.
Advertisement
Tutorials
+5.6k Golang : Configure crontab to poll every two minutes 8am to 6pm Monday to Friday
+9k Golang : Go as a script or running go with shebang/hashbang style
+16.8k Golang : Get own process identifier
+11.6k Golang : Fuzzy string search or approximate string matching example
+5.3k PHP : Hide PHP version information from curl
+5.2k Golang : Customize scanner.Scanner to treat dash as part of identifier
+17k Golang : Get the IPv4 and IPv6 addresses for a specific network interface
+16.5k Golang : File path independent of Operating System
+17.9k Golang : Iterate linked list example
+17.3k Google Chrome : Your connection to website is encrypted with obsolete cryptography
+15.6k Golang : rune literal not terminated error
+11k Golang : Replace a parameter's value inside a configuration file example