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.

Sign up for GitHub

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

Jump to bottom

cmd/trace: when using 'go tool trace trace.out', the memory got 100% #21062

Closed
ansencumt opened this issue Jul 18, 2017 · 9 comments
Closed

cmd/trace: when using 'go tool trace trace.out', the memory got 100% #21062

ansencumt opened this issue Jul 18, 2017 · 9 comments
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Unplanned

Comments

@ansencumt
Copy link

When using 'go tool trace trace.out', the memory got 100%, and the PC blocked.

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

go 1.8.3

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

image

What did you do?

image
@jessfraz jessfraz changed the title When using 'go tool trace trace.out', the memory got 100% cmd/trace: when using 'go tool trace trace.out', the memory got 100% Jul 18, 2017
@ianlancetaylor
Copy link
Contributor

Would it be possible to attach a copy of the trace.out file?

@ianlancetaylor ianlancetaylor added this to the Go1.10 milestone Jul 18, 2017
@ansencumt
Copy link
Author

@ianlancetaylor Yes, the trace file is a copy from server. The server`s system is Ubuntu.

@ianlancetaylor
Copy link
Contributor

@ansencumt I'm asking you to attach the trace file to this issue, so that we can try to recreate the problem ourselves.

@ansencumt
Copy link
Author

OK. But the file is too big.So I have to send it with email. The target email is the personal email ian@airs.com. I can`t find the communal email, sorry.

@hyangah
Copy link
Contributor

hyangah commented Aug 25, 2017

How big is the trace? The trace tool loads the entire trace into the memory.

@rsc
Copy link
Contributor

rsc commented Nov 22, 2017

@ianlancetaylor did ian@airs.com receive any trace? Maybe it's just too big and there's no bug here?

@ianlancetaylor
Copy link
Contributor

Neither of us received a trace.

@ianlancetaylor ianlancetaylor added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Nov 22, 2017
@ianlancetaylor
Copy link
Contributor

@ansencumt If this is still a problem, please send the trace to iant@golang.org. Thanks.

@ianlancetaylor ianlancetaylor modified the milestones: Go1.10, Unplanned Dec 6, 2017
@gopherbot
Copy link

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.)

@golang golang locked and limited conversation to collaborators Dec 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
5 participants
@rsc @ianlancetaylor @hyangah @ansencumt @gopherbot