You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\Administrator\AppData\Local\go-build
set GOENV=C:\Users\Administrator\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\Administrator\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\Administrator\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.16.4
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\Repos\github.com\VirtualMetric\virtualmetric-go\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\ADMINI~1\AppData\Local\Temp\2\go-build2746031420=/tmp/go-build -gno-record-gcc-switches
What did you do?
Our app makes many syscalls to collect different data for forensic analysis. Everytime when we got panic, it always happens in string operations (usually strconv.Itoa()) and always in "Remote Connection" analysis to detect remote attackers to pc. So right now, we disabled the remote connection analysis and we will test it. This issue usually happens after 12-24 hours. If issue would not happen, we will activate the remote connection analysis and disable Windows Defender to find out if Defender somehow crashing the app. App uses around 30-50 mb memory and there is always around 6 gb of free memory on the machine. Machine is running in Hyper-V virtualization as a VM. There is no dynamic memory or ballooning. All resources are allocated just for this VM. Here is where the issue happens:
Thank you for raising this issue. You mentioned that this issue occurs using strconv but the stack trace you supplied does not appear to include strconv.
We started the app with race detector and there are many issues and now we are solving them. I have one question about the race issues. Do you think memory corruption might happen after many data race issues? I see them in the race detector but app runs without issue. But I understand that, at some point, it will corrupt the memory?
App is still being in the test. If the panic happens, I will also share the latest data race issue.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Our app makes many syscalls to collect different data for forensic analysis. Everytime when we got panic, it always happens in string operations (usually strconv.Itoa()) and always in "Remote Connection" analysis to detect remote attackers to pc. So right now, we disabled the remote connection analysis and we will test it. This issue usually happens after 12-24 hours. If issue would not happen, we will activate the remote connection analysis and disable Windows Defender to find out if Defender somehow crashing the app. App uses around 30-50 mb memory and there is always around 6 gb of free memory on the machine. Machine is running in Hyper-V virtualization as a VM. There is no dynamic memory or ballooning. All resources are allocated just for this VM. Here is where the issue happens:
strconv.Itoa(session.Session) panics.
What did you expect to see?
I would expect not to see any issue during the string operation or get an error in return.
What did you see instead?
The text was updated successfully, but these errors were encountered: