# notebook crash

**URL:** <https://talk.observablehq.com/t/notebook-crash/1419>\
**Category:** Help\
**Created:** [November 20, 2018, 4:49pm UTC](https://talk.observablehq.com/t/notebook-crash/1419 "2018-11-20T16:49:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fil](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/fil/32/207_2.png) [@Fil](https://talk.observablehq.com/u/Fil)\
**Post date:** [November 20, 2018, 4:49pm UTC](https://talk.observablehq.com/t/notebook-crash/1419/1 "2018-11-20T16:49:18Z")

</div>

When I go to [https://beta.observablehq.com/@fil/reprojecting-vector-tiles](https://beta.observablehq.com/@fil/reprojecting-vector-tiles) with Firefox, connected as Fil, or Chrome in an anonymous window, everything is fine. But when I load it on Chrome, connected as Fil, or not connected, it crashes. I have no idea what to try now…

 ![45](https://canada1.discourse-cdn.com/flex030/uploads/observablehq/original/2X/7/773665c07adfa5a3b97b19b73ddf3aa41fa61d2f.png)

---

<div class="post-metadata">

**Author:** ![bumbeishvili](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/bumbeishvili/32/4220_2.png) [@bumbeishvili](https://talk.observablehq.com/u/bumbeishvili)\
**Post date:** [November 20, 2018, 6:30pm UTC](https://talk.observablehq.com/t/notebook-crash/1419/2 "2018-11-20T18:30:41Z")

</div>

> [@Fil](#):
>
> [Reprojecting Vector Tiles / Fil | Observable](https://beta.observablehq.com/@fil/reprojecting-vector-tiles)

Works fine in my chrome (mac os)

---

<div class="post-metadata">

**Author:** ![tom](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tom/32/2262_2.png) [@tom](https://talk.observablehq.com/u/tom)\
**Post date:** [November 20, 2018, 6:40pm UTC](https://talk.observablehq.com/t/notebook-crash/1419/3 "2018-11-20T18:40:33Z")

</div>

Hey Philippe,

Digging into this error (in Chromium) and it looks like _Failed to fetch_ indicates a network error - that our CORS configuration didn’t get across, or the network connection was unsteady, or possibly something in the middle truncated a response. I’ll keep digging for a potential issue on our end, but in the meantime can you check whether the failure occurs when you’re logged in with Firefox, and maybe try disabling any Chrome extensions that might be interrupting or modifying any requests?

Thanks,

-Tom

---

<div class="post-metadata">

**Author:** ![Fil](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/fil/32/207_2.png) [@Fil](https://talk.observablehq.com/u/Fil)\
**Post date:** [November 20, 2018, 7:10pm UTC](https://talk.observablehq.com/t/notebook-crash/1419/4 "2018-11-20T19:10:08Z")

</div>

The culprit was [https://api.observablehq.com/collection/@fil/geo](https://api.observablehq.com/collection/@fil/geo) which was apparently garbled in the local cache (the ERR\_CONTENT\_DECODING\_FAILED error in the console). Force reloading it solved the issue.