Unable to reproduce the issue on Win-10 using chrome reported version #63.0.3239.108 and latest canary #65.0.3304.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Navigated to settings chrome://settings/
2. Scrolled down to Start Page section
3. Set at least one start page i.e www.youtube.com
4. Restart chrome chrome://restart
5. Now blocked/pinned all the tab start pages opened.
6. Restarted chrome again chrome://restart.
7. Observed that chrome opened the start pages as BLOCKED tabs without duplicate them as normal tabs as expected.

reporter@ - Could you please check the issue on latest stable #65.0.3304.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 796287.mp4 2.9 MB

	796287.mp4 2.9 MB View Download

Just re-tested with your version and is still happening

Deleted: bugtest.mp4 2.2 MB

	bugtest.mp4 2.2 MB View Download

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Able to reproduce this issue on reported version 63.0.3239.108 and on latest canary 65.0.3307.0 using windows10, Ubuntu 14.04  with steps mentioned in comment#0. In Mac pinned tabs doesn't get opened on re-opening chrome.

Good Build: 58.0.2999.0 
Bad Build: 58.0.3000.0

You are probably looking for a change made after 447607 (known good), but no later than 447608 (first known bad).

https://chromium.googlesource.com/chromium/src/+log/e027f6a77853952285de14c8b9009c208b4c2c99..f9a9ef14dfdb45e70a898024b5c690ac4bf3a5e

Review-Url: https://codereview.chromium.org/2627363002

Suspecting the same changelog

@tmartino: Please confirm the issue and help in re-assigning if it is not related to your change.

Thanks!

Hi there,

When reimplementing this last year, we decided that this behavior was desired. This was because:

- Doing otherwise adds a lot of code complexity

- The number of users who have both pinned tabs and preferences-specified tabs is quite small

To give a better explanation of the complexity, it turns out to be quite difficult to determine when the pinned and preferences URLs overlap. We used to check for an exact URL text match, but it was highly unreliable.

This is because the pinned tab holds the *last* URL contained in that tab, rather than the URL you originally navigated to. Many major websites redirect you to another URL on load--for example, if I put "google.com" in my startup URLs, by the time the page loads, my URL is something like: "https://www.google.ca/?foo=bar&id=baz123". The only way to be sure that these shouldn't be duplicated would be to actually resolve the URL (i.e., attempt to load the page and see what happens)--and even then, it wouldn't account for lots of pages where the final URL you land on may change each time. It just doesn't make sense given how slow that would make startup.