Unable to reproduce the issue using #59.0.3071.115 on Win 7 as per the steps mentioned in comment #0. Observed chrome opened as maximized Window on opening second window also.

Could you please find the attached screen cast and let us know your observations.

Thanks!!

Deleted: Jul 18 2017 10-26 PM.webm 4.4 MB

	Jul 18 2017 10-26 PM.webm 4.4 MB View Download

Sorry for the confusion.
The issue is occurring on Android OS Samsung devices with Multiwindow feature.
Chrome version 59.x

Thank you for providing more feedback. Adding requester "sandeepkumars@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

Changing OS label to Android as per comment #3.

Thanks!!

Are you able to reproduce it now? 

Seems to be a critical issue, occurring on all Samsung devices.
Can it be checked on priority.

Issue is present in 55.x, 56.x ... 60.x


As per the logs :
onCreate() is initial step for application execution.
Chrome is calling  finishAndRemoveTask() on Create step. 
So Chrome application is exited and show the launcher app.
Concern is :  why Chrome is calling finishAndRemoveTask() API onCreate() step.

    at android.app.ActivityManagerProxy.finishActivity(ActivityManagerNative.java:3868)
     at android.app.Activity.finish(Activity.java:5356)
     at android.app.Activity.finishAndRemoveTask(Activity.java:5477)
     at org.chromium.base.ApiCompatibilityUtils.finishAndRemoveTask(ApiCompatibilityUtils.java:308)
     at org.chromium.chrome.browser.init.AsyncInitializationActivity.onCreate(AsyncInitializationActivity.java:1228)
     at android.app.Activity.performCreate(Activity.java:6933)
     at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1126)
     at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2908)
     at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3016)

Please let us know if there are any updates on this issue.

Please let us know if it would be possible to have this issue triaged.
Thank you!

@sandeepkumars, would it be possible to receive support on having this issue triaged?

@sandeepkumars, would it be possible to receive support on having this issue triaged?

@sandeepkumars, its similar to this : https://bugs.chromium.org/p/chromium/issues/detail?id=761915

Can we get an update on this issue.

I was able to repro this issue on Samsung Galaxy S6(SM-G920F)/NRD90M, Chrome: 60.0.3112.116. Issue repros only the 1st time Chrome is launched in both windows in multi-window mode. Relaunching chrome the next time, shows chrome instances on both the windows.

Adding video & logs @ http://go/chrome-androidlogs1/7/741243

Additional Info: Unable to repro this issue on Nexus5X/N2G48C, Chrome:60.0.3112.116

 Issue 761915  has been merged into this issue.

Chrome version 50 introduced multi-instance support for all devices running Android N+. To activate Chrome multi-instance on an N+ device:

1. Put the app in multi-window mode
2. Open 2+ tabs
3. From the app menu, select "Move to other window" on the tab you would like to move to a new Chrome window

Or

1. Put the app in multi-window mode
2. Long-press on a link a select "Open in other window" from the context menu



Chrome's multi-instance support was interacting poorly with Samsung's multi-instance, per the bug report, so we recently removed OEM specific multi-instance support: https://chromium-review.googlesource.com/c/chromium/src/+/647382. This fix will roll out in Chrome 63.

This will make Chrome behave consistently across devices. In multi-window, on Chrome 63+ tapping on the Chrome icon will refocus Chrome rather than launching a new instance. Chrome 63 is in the Dev channel if you would like to verify the fix.

On older versions of Android (M and below), Chrome still supports Samsung multi-instance and tapping on the Chrome icon will launch a second instance.