chrome://tracing gives a mixture of deprecation, tracing mismatch warnings, and end-recording error on Windows |
|
Issue descriptionChrome Version: 58.0.3013.0 (local build) OS: Windows 10 What steps will reproduce the problem? (1) Run Chrome with --enable-heap-profiling (and --enable-logging). (2) Open chrome://tracing and start Recording. (3) Open a new tab (I think I actually reloaded the tab, because it crashed). (4) Stop the recording. (5) Save the trace. What is the expected result? Expect not to see (m)any warnings or errors from tracing.js What happens instead? Several warnings, and an error, were reported: [27652:45540:0214/133753.068:WARNING:CONSOLE(1358)] "/deep/ combinator is deprecated. See https://www.chromestatus.com/features/6750456638341120 for more details.", source: chrome://tracing/tracing.js (1358) [27652:45540:0214/133956.852:WARNING:CONSOLE(2752)] "Unrecognized metadata name: IsTimeTicksHighResolution", source: chrome://tracing/tracing.js (2752) [27652:45540:0214/133957.311:WARNING:CONSOLE(2752)] "Nestable async BEGIN event at 2424427658379 with name=ProcessMemoryDump and id={scope: ptr, id: 0x6} was unmatched.", source: chrome://tracing/tracing.js (2752) [27652:45540:0214/133957.394:WARNING:CONSOLE(2752)] "Different phases of MemoryDumpManager::InvokeOnMemoryDump provided values for argument dump_provider.name. The last provided value will be used.", source: chrome://tracing/tracing.js (2752) [27652:45540:0214/134006.775:WARNING:CONSOLE(2752)] "Size provided by memory allocator dump 'malloc'20.2 MiB) is less than the aggregated size of its children (20.3 MiB).", source: chrome://tracing/tracing.js (2752) [27652:45540:0214/134139.103:WARNING:CONSOLE(4930)] "'webkitURL' is deprecated. Please use 'URL' instead.", source: chrome://tracing/tracing.js (4930) [27652:45540:0214/134249.380:ERROR:CONSOLE(1598)] "Uncaught (in promise) Error: Error occured at /json/end_recording_compressed", source: chrome://tracing/tracing.js (1598)
,
Feb 15 2017
I will be realistic here: given the fact that there is nobody working fulltime on the UI, but we steal bandwidth of known suspects on demand, I don't think that the warnings coming from TraceViewer UI through the JS console is anything that we'll ever manage to deal with (what you see is a side effect of enalbing logging that spits out on stdout the JS console. Try to got to facebook.com and see what happens :P) The only red-herring is "Size provided by memory allocator dump 'malloc'20.2 MiB) is less than the aggregated size of its children (20.3 MiB)" which should also show in the form of an exclamation mark on the malloc cell in the table. It sounds like the malloc_dump_provider is providing data that makes less sense (i.e. it's saying that the bytes for objects allocated by malloc is < the "outer" memory used by malloc which should include freelists, fragmentation and whatnot)
,
Feb 15 2017
Re #2: Right; there's definitely a mix of priorities in here; we should focus on the bogus-data issues but it'd be good to clean up some of the other logging so real warnings don't get lost in the noise. |
|
►
Sign in to add a comment |
|
Comment 1 by w...@chromium.org
, Feb 14 2017