{"id":105711,"date":"2021-09-20T07:00:00","date_gmt":"2021-09-20T14:00:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/oldnewthing\/?p=105711"},"modified":"2021-09-20T06:55:35","modified_gmt":"2021-09-20T13:55:35","slug":"20210920-00","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20210920-00\/?p=105711","title":{"rendered":"What does this mean? The caller specified wait timed out before the operation completed because a host termination is in queued"},"content":{"rendered":"<p>So your program is running along, minding its own business, and then it crashes with exception <code>0x80070bfe<\/code> = &#8220;The caller specified wait timed out before the operation completed because a host termination is in queued&#8221;, or possibly <code>0x80070bfd<\/code> = &#8220;The caller specified wait timed out before the operation completed.&#8221; This is completely gibberish. What does it mean? I don&#8217;t remember specifying any timeout, and I don&#8217;t know what a host termination is.<\/p>\n<p>It means that you called <code>Core\u00adApplication.<wbr \/>Create\u00adNew\u00adView<\/code> while your app was suspending or resuming.<\/p>\n<p>This particular error is generated deep inside the windowing infrastructure code, and the problem manifests itself in an internal timeout. The inner low-level component reports that an operation timed out, and that&#8217;s the reason why the error message talks about a timeout.<\/p>\n<p>This error is then propagated all the way up the chain back to the application without anybody ever realizing, &#8220;Hey, this error may not make sense to the person I&#8217;m reporting it to.&#8221; The error message made sense at the point of origination, but by the time the error reaches the application, the original context of the error is long gone, and the message makes no sense unless you&#8217;re wearing windowing infrastructure-colored glasses.<\/p>\n<p>Sorry.<\/p>\n<p><b>Bonus chatter<\/b>: Sometimes the error manifests itself in error <code>0X87B20C08<\/code>, which doesn&#8217;t even have an associated message!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>An error message written with infrastructure-colored glasses.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-105711","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"<p>An error message written with infrastructure-colored glasses.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/105711","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=105711"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/105711\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=105711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=105711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=105711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}