-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic when run test #40
Comments
之前我也遇到过这个问题,但是不能稳定重现。你那边是否能稳定重现? 是上游 gomq 的一个问题。 |
我这边也有这个问题,脚本参考的是http://myzhan.github.io/2016/03/01/write-a-load-testing-tool-in-golang/ |
能稳定复现吗?其它东西的版本麻烦贴一下,还有操作系统。
weigun <notifications@github.com>于2018年7月23日 周一上午11:50写道:
… 我这边也有这个问题,脚本参考的是
http://myzhan.github.io/2016/03/01/write-a-load-testing-tool-in-golang/
go版本是1.10
./stest --master-host=127.0.0.1 --master-port=5557 --rpc=zeromq
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#40 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA6NtZKpqmOhSttLG9QbYtf7ba6Cqw_Xks5uJUf9gaJpZM4VX7AB>
.
|
除了遇到这个问题外,还有其他报错,master收到u'runtime error: invalid memory address or nil pointer dereference'的报错 另外,如果rpc使用socket,会提示out of memory import boomer "github.com/myzhan/boomer" import ( func now() int64 { func test_http() { func main() {
}`
runtime stack: goroutine 21 [running]: goroutine 1 [chan receive]: goroutine 19 [syscall]: goroutine 4 [select]: goroutine 5 [chan receive]: goroutine 22 [running]: goroutine 23 [chan receive]: goroutine 24 [chan receive]: goroutine 25 [select, locked to thread]: |
@weigun 两个问题
|
@myzhan |
panic: runtime error: index out of range
goroutine 3584 [running]:
github.com/zeromq/gomq.(*Socket).Recv(...)
/Users/zhangzhen/serverproj/src/github.com/zeromq/gomq/socket.go:115
github.com/myzhan/boomer.(*gomqSocketClient).recv(0xc42026ec20)
/Users/zhangzhen/serverproj/src/github.com/myzhan/boomer/client_gomq.go:86 +0x115
created by github.com/myzhan/boomer.newZmqClient
/Users/zhangzhen/serverproj/src/github.com/myzhan/boomer/client_gomq.go:79 +0x717
The text was updated successfully, but these errors were encountered: