Profiler does not include parser performance for pages served as XML
Reported by
t...@r.je,
Aug 5
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.84 Safari/537.36 Steps to reproduce the problem: 1. Serve a page as application/xml or application/xhtml+xml 2. Benchmark page using "Start profiling and reload page" in the performance tab 3. Press stop 4. View profiler output What is the expected behavior? "Parse XML" should appear in the profile as "Parse HTML" does with content served as text/html. What went wrong? The XML parsing time is either incorrectly labelled (though I can't see what it may be) or is not included in the profiler. Did this work before? N/A Chrome version: 68.0.3440.84 Channel: stable OS Version: Arch Flash Version:
,
Aug 6
tom@ - Thanks for filing the issue...!! Could you please provide any sample test file/url to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Aug 13
|
|||
►
Sign in to add a comment |
|||
Comment 1 by vamshi.kommuri@chromium.org
, Aug 6