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

Issue 650220 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Incomplete file saved for 'Record Allocation Timeline' in 'Profile' section.

Reported by rk...@etouch.net, Sep 26 2016

Issue description

Chrome Version: 55.0.2872.0 Revision 5264ac775e58852ece697a6e26117d72181c4f41-refs/heads/master@{#420859}(32/64 bit)
OS: Windows (7,8,10), Mac(10.10.5,10.11.4),Linux

What steps will reproduce the problem?
(1) Launch chrome, open dev tools window and navigate to 'Profile' section.
(2) Click on 'Record Allocation Timeline' radio button and start recording then stop it.
(3) Now click on save and save file observe saving status under snapshot1 name.

Actual: Even after complete save status remains 'saving.....0%'.

Expected: After complete save status should change to file size.

This is a regression issue, broken in 'M-55', will soon update the other info:

Good build: 55.0.2866.0
Bad Build: 55.0.2867.0


 
Actual_Save.mp4
847 KB View Download
Expected_Save.mp4
652 KB View Download
Cc: pfeldman@chromium.org
Labels: ReleaseBlock-Stable hasbisect-per-revision
Owner: jam@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 55.0.2866.0 (Revision: 419628).
Bad build: 55.0.2867.0 (Revision: 419930).

You are probably looking for a change made after 419645 (known good), but no later than 419646 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/48cc4735421d93aee9958d76e95d7a80c67ed9f1..edcd8b01496d777037b3752d82ac64a16b6cedd0


Note: Adding RB Label as this is a recent Regression. Please remove if not required.
@jam -- Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.
Thank You.

Comment 2 by ajha@chromium.org, Sep 29 2016

Cc: scottmg@chromium.org
Still seen on chrome version:55.0.2875.0 on Linux Ubuntu 14.04.

jam@: Could you please check the issue and update this thread.
Just to update the latest behavior of the bug, issue is still reproducible on Windows-10 using chrome latest Dev #55.0.2873.0.

Comment 4 by ajha@chromium.org, Oct 7 2016

Friendly ping to get an update on this issue.

Comment 5 by ajha@chromium.org, Oct 14 2016

Ping for an update.


jam@ Ping! can we know what's the status of the fix,since we are about to promote M55 to Beta and we need to get the fix into branch soon.

Comment 7 by gov...@chromium.org, Oct 26 2016

**** Bulk edit -  please ignore if not applicable ****

A friendly reminder that M55 Stable is launch is coming soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!

Comment 8 by jam@chromium.org, Oct 27 2016

I missed this bug, sorry. looking

Comment 9 by jam@chromium.org, Oct 27 2016

Status: WontFix (was: Assigned)
This is the same as  bug 652937 , which was fixed on trunk (10/5) before branch point. I've verified that it works on m55 branch.

Sign in to add a comment