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
+6.8k Golang : Check if password length meet the requirement
+4.7k Linux : sudo yum updates not working
+22.5k Golang : How to read JPG(JPEG), GIF and PNG files ?
+8.8k Golang : Find duplicate files with filepath.Walk
+8.7k Golang : Set or add headers for many or different handlers
+5.4k Golang : How to deal with configuration data?
+41.1k Golang : How to check if a string contains another sub-string?
+13.7k Golang : Query string with space symbol %20 in between
+11.5k Golang : Delay or limit HTTP requests example
+7.6k Golang : Shuffle strings array
+13.3k CodeIgniter : "Fatal error: Cannot use object of type stdClass as array" message
+14k Generate salted password with OpenSSL example