Skip to content
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

runtime: Random crash from Windows Server 2019 #61411

Closed
BVoychev opened this issue Jul 18, 2023 · 3 comments
Closed

runtime: Random crash from Windows Server 2019 #61411

BVoychev opened this issue Jul 18, 2023 · 3 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@BVoychev
Copy link

What version of Go are you using (go version)?

$ go version
1.16.15

Does this issue reproduce with the latest release?

Issue was reproduced with go version 1.19.

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
OS: Windows Svr 2019 version 1809

What did you do?

I have started a go application on Windows Server 2019. After a few months the application started to randomly crash.

What did you expect to see?

No crash.

What did you see instead?

A go application running on Windows Server randomly crashes with the following error:

runtime stack:
runtime: unexpected return pc for sigtramp called from 0xf77e3fef80
...

runtime.throw(0xdf5d63, 0x2a)
    C:/Program Files/Go/src/runtime/panic.go:1117 +0x79
runtime.sigpanic()
    C:/Program Files/Go/src/runtime/signal_windows.go:233 +0x317
runtime.gentraceback(0xffffffffffffffff, 0xffffffffffffffff, 0x0, 0xc000c9f800, 0x0, 0x0, 0x64, 0x0, 0x0, 0x0, ...)
    C:/Program Files/Go/src/runtime/traceback.go:249 +0x13c9
runtime.traceback1(0xffffffffffffffff, 0xffffffffffffffff, 0x0, 0xc000c9f800, 0x0)
    C:/Program Files/Go/src/runtime/traceback.go:732 +0x105
runtime.traceback(...)
    C:/Program Files/Go/src/runtime/traceback.go:686
runtime.tracebackothers(0xc00040f500)
    C:/Program Files/Go/src/runtime/traceback.go:951 +0x173
runtime.lastcontinuehandler(0xf77e3ff470, 0xf77e3fef80, 0xc00040f500, 0x0)
    C:/Program Files/Go/src/runtime/signal_windows.go:218 +0x265
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 18, 2023
@qmuntal qmuntal added OS-Windows NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Jul 18, 2023
@qmuntal
Copy link
Member

qmuntal commented Jul 18, 2023

@bcmills @cherrymui the failure mode seems to be the same as in #50144.

@mknyszek
Copy link
Contributor

It's really hard to tell from just the information provided. That stack (tracebackothers) happens whenever there's any kind of throw. Do you have a way to reproduce the issue?

I also want to point out that 1.19 isn't going to be supported anymore in just a few weeks when Go 1.21 comes out. Can you reproduce with even newer Go versions?

Thanks.

@mknyszek mknyszek added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jul 26, 2023
@mknyszek mknyszek added this to the Backlog milestone Jul 26, 2023
@gopherbot
Copy link
Contributor

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@gopherbot gopherbot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 26, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in Go Compiler / Runtime Aug 26, 2023
@golang golang locked and limited conversation to collaborators Aug 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

4 participants