Fix fatal error: evacuation not done in time problem


5386 views 25th September 2014


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

+9.2k Golang : Validate IPv6 example


+14.3k Golang : Normalize unicode strings for comparison purpose


+7k Golang : Word limiter example


+10.9k Android Studio : Create custom icons for your application example


+21.9k Golang : Read directory content with filepath.Walk()


+14k Golang : GUI with Qt and OpenCV to capture image from camera


+7.2k Golang : Shuffle strings array


+7.3k Golang : Example of how to detect which type of script a word belongs to


+18.5k Golang : Check whether a network interface is up on your machine


+6.1k Grep : How to grep for strings inside binary data


+6.9k Golang : Dealing with postal or zip code example


+8k Golang : How to check variable or object type during runtime?