Fix fatal error: evacuation not done in time problem


4258 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.7k Swift : Convert (cast) Int or int32 value to CGFloat


+25.5k Golang : Get and Set User-Agent examples


+4.9k Golang : How to iterate a slice without using for loop?


+8.8k Golang : Pagination with go-paginator configuration example


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


+4.2k Fix ERROR 2003 (HY000): Can't connect to MySQL server on 'IP address' (111)


+9.6k Golang : Calculations using complex numbers example


+36.4k Golang : How to iterate over a []string(array)


+9k Golang : Split strings into command line arguments


+11k Golang : How to get URL port?


+10.3k Golang : Generate Code128 barcode


+6.1k Golang : Gomobile init produce "iphoneos" cannot be located error