New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 703313 link

Starred by 1 user
Status: WontFix
Owner:
w...@chromium.org
Closed: May 2017
Cc:
█ ajwong@chromium.org
etienneb@chromium.org
erikc...@chromium.org
█ picksi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug
Hotlist-MemoryInfra

Blocking:
issue 686208



Sign in to add a comment

Native heap profiling gives bogus/garbage object type names under Windows

Project Member Reported by w...@chromium.org, Mar 20 2017 
What steps will reproduce the problem?
(1) Run Chrome with --enable-heap-profiling[=native]
(2) Take a memory-infra dump & symbolize it.
(3) Load it into chrome://tracing

What is the expected result?

Expect sensible object type names in the output.

What happens instead?

Object type names are garbage; they look like uninitialized data, or possible wrong character encoding.

Comment 1 by w...@chromium.org, Apr 13 2017

Cc: erikc...@chromium.org etienneb@chromium.org ajwong@chromium.org
Guys, I'm unable to repro this in recent traces (at least before I run them through the symbolizer script ;) - are you?

Comment 2 by w...@chromium.org, May 26 2017

Status: WontFix (was: Assigned)
Closing out based on no longer seeing this; please re-open if you see it cropping up.

Comment 3 by etienneb@chromium.org, May 26 2017 

I believe this was fixed with this patch:
  https://bugs.chromium.org/p/chromium/issues/detail?id=713741
►

Sign in to add a comment