[NextBrowser] No need to use ProcessSingleton for NextBrowser

Fixes issue of browser not launching after change of network info

Change-Id: Ic21048732d1747c1784221b53bc1607642bce227

diff --git a/chrome/browser/BUILD.gn b/chrome/browser/BUILD.gn
index 637c53147ce135995fe2e0e2f1c934ab7286e40c..a3f5fc47d17829dc94cb7813988373fec242342c 100644 (file)
--- a/chrome/browser/BUILD.gn
+++ b/chrome/browser/BUILD.gn
@@ -113,7 +113,8 @@ buildflag_header("buildflags") {
 
   # Android and ChromeOS don't support multiple browser processes, so they don't
   # employ ProcessSingleton.
-  if (is_android || is_chromeos) {
+  # Neither does Tizen TV.
+  if (is_android || is_chromeos || is_samsung_next_browser) {
     flags += [ "ENABLE_PROCESS_SINGLETON=0" ]
   } else {
     flags += [ "ENABLE_PROCESS_SINGLETON=1" ]