mirror of
https://github.com/crazybber/awesome-patterns.git
synced 2024-11-22 04:36:02 +03:00
resource leak go routine demo
This commit is contained in:
parent
d9d6a823f7
commit
08e01c5a9c
49
concurrency/goroutine_leak/main.go
Normal file
49
concurrency/goroutine_leak/main.go
Normal file
@ -0,0 +1,49 @@
|
||||
package main
|
||||
|
||||
import "fmt"
|
||||
|
||||
// The goroutine has a few paths to termination:
|
||||
// • When it has completed its work.
|
||||
// • When it cannot continue its work due to an unrecoverable error.
|
||||
// • When it’s told to stop working
|
||||
|
||||
/**
|
||||
We get the first two paths for free—these paths are your algorithm—but what about
|
||||
work cancellation? This turns out to be the most important bit because of the net‐
|
||||
work effect: if you’ve begun a goroutine, it’s most likely cooperating with several other
|
||||
goroutines in some sort of organized fashion.
|
||||
**/
|
||||
|
||||
func main() {
|
||||
|
||||
}
|
||||
|
||||
// Here we see that the main goroutine passes a nil channel into doWork. Therefore, the
|
||||
// strings channel will never actually gets any strings written onto it, and the goroutine
|
||||
// containing doWork will remain in memory for the lifetime of this process (we would
|
||||
// even deadlock if we joined the goroutine within doWork and the main goroutine).
|
||||
// In this example, the lifetime of the process is very short, but in a real program, gorou‐
|
||||
// tines could easily be started at the beginning of a long-lived program. In the worst
|
||||
// case, the main goroutine could continue to spin up goroutines throughout its life,
|
||||
// causing creep in memory utilization.
|
||||
func resourceLeak() {
|
||||
doWork := func(strings <-chan string) <-chan interface{} {
|
||||
completed := make(chan interface{})
|
||||
go func() {
|
||||
defer fmt.Println("doWork exited.")
|
||||
defer close(completed)
|
||||
for s := range strings {
|
||||
// Do something interesting
|
||||
fmt.Println(s)
|
||||
}
|
||||
}()
|
||||
return completed
|
||||
}
|
||||
doWork(nil)
|
||||
// Perhaps more work is done here
|
||||
fmt.Println("Done.")
|
||||
}
|
||||
|
||||
func cancellationSignal() {
|
||||
|
||||
}
|
21
for-range-semantics/main.go
Normal file
21
for-range-semantics/main.go
Normal file
@ -0,0 +1,21 @@
|
||||
package main
|
||||
|
||||
import "fmt"
|
||||
|
||||
type user struct {
|
||||
name string
|
||||
email string
|
||||
}
|
||||
|
||||
func main() {
|
||||
users := []user{
|
||||
{"Bill", "bill@email.com"},
|
||||
{"Lisa", "lisa@email.com"},
|
||||
{"Nancy", "nancy@email.com"},
|
||||
{"Paul", "paul@email.com"},
|
||||
}
|
||||
|
||||
for i, u := range users {
|
||||
fmt.Println(i, u)
|
||||
}
|
||||
}
|
Loading…
Reference in New Issue
Block a user