Solve a stack_use_after_scope issue in sockaddr_resolver_test

7 years ago · f0798f91ff
parent 9a4c6b31e5
commit f0798f91ff
1 changed files with 3 additions and 1 deletions
--- a/test/core/client_channel/resolvers/sockaddr_resolver_test.cc
+++ b/test/core/client_channel/resolvers/sockaddr_resolver_test.cc
@ -63,8 +63,10 @@ static void test_succeeds(grpc_resolver_factory* factory, const char* string) {
  grpc_resolver_next_locked(resolver, &on_res_arg.resolver_result,
                            on_resolution);
  GRPC_RESOLVER_UNREF(resolver, "test_succeeds");
-
  grpc_uri_destroy(uri);
+  /* Flush ExecCtx to avoid stack-use-after-scope on on_res_arg which is
+   * accessed in the closure on_resolition_cb */
+  grpc_core::ExecCtx::Get()->Flush();
 }

 static void test_fails(grpc_resolver_factory* factory, const char* string) {