Enable init_stack_vars for non-official Debug Windows builds

Debug build is fixed with: crrev.com/c/1973353

Bug: 977230, 1030261
Change-Id: Idcb24d092247f6bc7438c74b6405b4b93539507d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970852
Commit-Queue: Vitaly Buka <vitalybuka@chromium.org>
Reviewed-by: Vitaly Buka <vitalybuka@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728840}

build/config/compiler/BUILD.gn

@@ -143,11 +143,10 @@ declare_args() {
   # rest with 0xAA. This makes behavior of uninitialized memory bugs consistent,
   # recognizeble in debugger, and crashes memory accesses by uninitialized
   # pointers.
-  # TODO(vitalybuka): investigate why some debug windows bots fail tests.
+  # TODO(vitalybuka):
   # 'is_android' breaks content_shell_test_apk on android-kitkat-arm-rel.
   # 'use_xcode_clang' may call old clang.
-  init_stack_vars = !is_android && !(is_win && is_debug) && !use_xcode_clang &&
-                    !is_official_build
+  init_stack_vars = !is_android && !use_xcode_clang && !is_official_build
 }
 
 declare_args() {