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.7k Golang : Calculate pivot points for a cross
+40k Golang : UDP client server read write example
+6.3k Golang : How to search a list of records or data structures
+5.2k Golang : Get FX sentiment from website example
+7.5k Golang : Detect sample rate, channels or latency with PortAudio
+5.3k Golang : How to deal with configuration data?
+48k Golang : How to convert JSON string to map and slice
+14.3k Android Studio : Use image as AlertDialog title with custom layout example
+14k Golang : Reverse IP address for reverse DNS lookup example
+5.9k Golang : Extract unicode string from another unicode string example
+10.9k Golang : Generate random elements without repetition or duplicate
+5.7k Golang : Fix opencv.LoadHaarClassifierCascade The node does not represent a user object error