- Learning Concurrency in Kotlin
- Miguel Angel Castiblanco Torres
- 376字
- 2021-08-05 10:46:43
Race conditions
Race conditions, perhaps the most common error when writing concurrent code, happen when concurrent code is written but is expected to behave like sequential code. In more practical terms, it means that there is an assumption that concurrent code will always execute in a particular order.
For example, let's say that you are writing a function that has to concurrently fetch something from a database and call a web service. Then it has to do some computation once both operations are completed. It would be a common mistake to assume that going to the database will be faster, so many people may try to access the result of the database operation as soon as the web service operation is done, thinking that by that time the information from the database will always be ready. Whenever the database operation takes longer than the webservice call, the application will either crash or enter an inconsistent state.
A race condition happens, then, when a concurrent piece of software requires semi-independent operations to complete in a certain order to be able to work correctly. And this is not how concurrent code should be implemented.
Let's see a simple example of this:
data class UserInfo(val name: String, val lastName: String, val id: Int)
lateinit var user: UserInfo
fun main(args: Array<String>) = runBlocking {
asyncGetUserInfo(1)
// Do some other operations
delay(1000)
println("User ${user.id} is ${user.name}")
}
fun asyncGetUserInfo(id: Int) = async {
user = UserInfo(id = id, name = "Susan", lastName = "Calvin")
}
The main() function is using a background coroutine to get the information of a user, and after a delay of a second (simulating other tasks), it prints the name of the user. This code will work because of the one second delay. If we either remove that delay or put a higher delay inside asyncGetUserInfo(), the application will crash. Let's replace asyncGetUserInfo() with the following implementation:
fun asyncGetUserInfo(id: Int) = async {
delay(1100)
user = UserInfo(id = id, name = "Susan", lastName = "Calvin")
}
Executing this will cause main() to crash while trying to print the information in user, which hasn't been initialized. To fix this race condition, it is important to explicitly wait until the information has been obtained before trying to access it.
- Mastering Entity Framework Core 2.0
- Java高并發核心編程(卷2):多線程、鎖、JMM、JUC、高并發設計模式
- LabVIEW入門與實戰開發100例
- .NET 4.0面向對象編程漫談:基礎篇
- Android 9 Development Cookbook(Third Edition)
- Wireshark Network Security
- Practical DevOps
- 網絡爬蟲原理與實踐:基于C#語言
- 可解釋機器學習:模型、方法與實踐
- Scala程序員面試算法寶典
- FPGA Verilog開發實戰指南:基于Intel Cyclone IV(進階篇)
- Getting Started with React Native
- Android編程權威指南(第4版)
- Hands-On Dependency Injection in Go
- 精益軟件開發管理之道