Fix fatal error: evacuation not done in time problem


5508 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

+6.1k Unix/Linux : Use netstat to find out IP addresses served by your website server


+15.9k Golang : Loop each day of the current month example


+18k Golang : How to remove certain lines from a file


+4.6k Fix Google Analytics Redundant Hostnames problem


+9.2k Facebook : Getting the friends list with PHP return JSON format


+7.6k Javascript : How to check a browser's Do Not Track status?


+12.6k Golang : http.Get example


+25.1k Golang : Convert long hexadecimal with strconv.ParseUint example


+9.7k Golang : Function wrapper that takes arguments and return result example


+37.5k Golang : Comparing date or timestamp


+7.5k Golang : Test if an input is an Armstrong number example


+23.1k Golang : Get ASCII code from a key press(cross-platform) example