<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Stadia Crashing on Pixlebook go in Stadia on Chrome</title>
    <link>https://community.stadia.com/t5/Stadia-on-Chrome/Stadia-Crashing-on-Pixlebook-go/m-p/37960#M2202</link>
    <description>&lt;P&gt;I've seen this happen on my regular Pixelbook during "heavy" Internet use times (i.e. three kids and wife all schooling/WFH). Have not been able to test a lot of scenarios, but I will say that Stadia on my Chromebook has been a generally subpar experience compared to on TV with Chromecast (which is unfortunate given the whole "play anywhere" flexibility of Stadia; so far that's not been my experience).&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2020 13:17:24 GMT</pubDate>
    <dc:creator>Samas</dc:creator>
    <dc:date>2020-11-05T13:17:24Z</dc:date>
    <item>
      <title>Stadia Crashing on Pixlebook go</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Stadia-Crashing-on-Pixlebook-go/m-p/37798#M2196</link>
      <description>&lt;P&gt;I have not been able to start a game from chrome on my Pixelbook Go for a while now. It used to work but now it just hangs on checking connection then says reopen game to play. I am on wifi with Gigabit fiber to the house and I am getting 240 down 140 up. This just started happening. Chrome OS is up to date. Anyone else have this issue?&lt;/P&gt;</description>
      <pubDate>Mon, 02 Nov 2020 15:15:54 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Stadia-Crashing-on-Pixlebook-go/m-p/37798#M2196</guid>
      <dc:creator>AgentSmith</dc:creator>
      <dc:date>2020-11-02T15:15:54Z</dc:date>
    </item>
    <item>
      <title>Re: Stadia Crashing on Pixlebook go</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Stadia-Crashing-on-Pixlebook-go/m-p/37799#M2197</link>
      <description>&lt;P&gt;Have you ever reset the Chrome browser, deleted cache and cookies?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Nov 2020 15:27:11 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Stadia-Crashing-on-Pixlebook-go/m-p/37799#M2197</guid>
      <dc:creator>defischerrockt</dc:creator>
      <dc:date>2020-11-02T15:27:11Z</dc:date>
    </item>
    <item>
      <title>Re: Stadia Crashing on Pixlebook go</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Stadia-Crashing-on-Pixlebook-go/m-p/37960#M2202</link>
      <description>&lt;P&gt;I've seen this happen on my regular Pixelbook during "heavy" Internet use times (i.e. three kids and wife all schooling/WFH). Have not been able to test a lot of scenarios, but I will say that Stadia on my Chromebook has been a generally subpar experience compared to on TV with Chromecast (which is unfortunate given the whole "play anywhere" flexibility of Stadia; so far that's not been my experience).&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2020 13:17:24 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Stadia-Crashing-on-Pixlebook-go/m-p/37960#M2202</guid>
      <dc:creator>Samas</dc:creator>
      <dc:date>2020-11-05T13:17:24Z</dc:date>
    </item>
  </channel>
</rss>

