dongyou26216708 2018-12-26 12:33
浏览 54
已采纳

所有goroutine都处于睡眠状态-死锁(无限循环+选择)

I have an app which creates, every few seconds, a routine fetching the current price from an API. It then sends the response to Monitor routine for analysis. If the Monitor finds that the price has changed significantly, it sends a notification.

It works fine if the delay between each go routine is large. It doesn't, if it is small: "fatal error: all goroutines are asleep - deadlock!" gets triggered and the program crashes.

I'm guessing (?) that the deadlock is caused by either (1) the Monitor being flooded with new price information (and not managing to analyse them timely); or (2) the Main function being flooded by messages from the Monitor.

There is probably also some weakness in the fact that the Main function appends the new price to a slice, while the Monitor is iterating through it.

How can this be resolved? Reading other posts here I thought that the "select" statement would be the magic cure, but it doesn't seem to be...

func main() {
    ec := make(chan entry, 10)
    mce := make (chan entry, 10)
    mcn := make(chan string, 10)

    go monitor(mce, mcn)

    for {
        go fetchData(ec)
    select {
        // get entries
        case newEntry := <- ec:
            log = append(log, newEntry)
            mce <- newEntry
        default:
            {}
        }

        //check if any notifications received
        select {
        case newMsg := <- mcn:
            fmt.Println(newMsg)
        default:
            {}
        }

        delay()
    }
}

func monitor(mce <-chan entry, mcn chan<- string) {


    for {
        newEntry = <- mce

        for _, item := range log {
            // here - do some analysis comparing the newEntry against previous entries
            // (essentially to see if notification should be triggered)
        }

        if should_send_notification {
            mcn <- msg
        }

    }
}

func fetchData(ec chan<- entry) {

    // here some code fetching newEntry from APIs

    // send the newEntry back to the main function
    ec <- newEntry

}
  • 写回答

1条回答 默认 最新

  • douxiyi2418 2018-12-26 13:37
    关注

    You only need merge the select on one and remove the default statement on main function. Removing the default statement you don't need a delay() function because the select-case works blocking and waiting some message from channels:

    func main() {
        ec := make(chan entry, 10)
        mce := make (chan entry, 10)
        mcn := make(chan string, 10)
    
        go monitor(mce, mcn)
        go fetchData(ec)
        for {
            select {
                // get entries
                case newEntry := <- ec:
                    log = append(log, newEntry)
                    mce <- newEntry
                //check if any notifications received
                case newMsg := <- mcn:
                    fmt.Println(newMsg)
            }
        }
    }
    

    The fetchData(ec) is convenient to implement like blocking and do not call it continuously:

    func fetchData(ec chan<- entry) {
    
        for {
            // here some code fetching newEntry from APIs
            // waiting data
    
            // send the newEntry if I get data
            ec <- newEntry
        }
    
    }
    
    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 如何在scanpy上做差异基因和通路富集?
  • ¥20 关于#硬件工程#的问题,请各位专家解答!
  • ¥15 关于#matlab#的问题:期望的系统闭环传递函数为G(s)=wn^2/s^2+2¢wn+wn^2阻尼系数¢=0.707,使系统具有较小的超调量
  • ¥15 FLUENT如何实现在堆积颗粒的上表面加载高斯热源
  • ¥30 截图中的mathematics程序转换成matlab
  • ¥15 动力学代码报错,维度不匹配
  • ¥15 Power query添加列问题
  • ¥50 Kubernetes&Fission&Eleasticsearch
  • ¥15 報錯:Person is not mapped,如何解決?
  • ¥15 c++头文件不能识别CDialog