# Can't visualize CPTAC pathology image

**URL:** <https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281>\
**Category:** Support\
**Created:** [June 3, 2022, 3:07pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281 "2022-06-03T15:07:18Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![kirbyju](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/kirbyju/32/70_2.png) [@kirbyju](https://discourse.canceridc.dev/u/kirbyju)\
**Post date:** [June 3, 2022, 3:07pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/1 "2022-06-03T15:07:18Z")

</div>

Hi, I was just browsing through some CPTAC-BRCA pathology data and when I go to any of the visualize buttons for the couple of patients I tried nothing loads. Here’s an example URL:

[https://viewer.imaging.datacommons.cancer.gov/slim/studies/2.25.25148242785680290844136875845052620468/series/1.3.6.1.4.1.5962.99.1.134619657.2139837279.1640812159497.2.0](https://viewer.imaging.datacommons.cancer.gov/slim/studies/2.25.25148242785680290844136875845052620468/series/1.3.6.1.4.1.5962.99.1.134619657.2139837279.1640812159497.2.0)

I’m using Chrome for my browser.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/fedorov/32/3_2.png) [@fedorov](https://discourse.canceridc.dev/u/fedorov)\
**Post date:** [June 3, 2022, 3:30pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/2 "2022-06-03T15:30:52Z")

</div>

Interesting - when I try the link you shared, it works for me (see screencapture linked below). Can you enable Developer console (View \> Developer tools) and see if there are any error messages? What version of Chrome do you have? (mine is Version 101.0.4951.64 (Official Build) (x86\_64) and I am on mac).

> **[2022-06-03\_11-28-27.gif](https://www.screencast.com/t/4tXtJk8CVK8)**
>
> Shared from Screencast.com

---

<div class="post-metadata">

**Author:** ![pieper](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/pieper/32/10_2.png) [@pieper](https://discourse.canceridc.dev/u/pieper)\
**Post date:** [June 3, 2022, 3:47pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/3 "2022-06-03T15:47:39Z")

</div>

When I first clicked on the link from Justin I got an error that the metadata could not be loaded, but when I did a hard reload (shift-command-R on mac Chrome) it did load okay.

---

<div class="post-metadata">

**Author:** ![kirbyju](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/kirbyju/32/70_2.png) [@kirbyju](https://discourse.canceridc.dev/u/kirbyju)\
**Post date:** [June 3, 2022, 3:55pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/4 "2022-06-03T15:55:38Z")

</div>

Output from the console:

GET [https://viewer.imaging.datacommons.cancer.gov/slim/studies/2.25.25148242785680290844136875845052620468/series/1.3.6.1.4.1.5962.99.1.134619657.2139837279.1640812159497.2.0](https://viewer.imaging.datacommons.cancer.gov/slim/studies/2.25.25148242785680290844136875845052620468/series/1.3.6.1.4.1.5962.99.1.134619657.2139837279.1640812159497.2.0) 404  
main.b6718321.js:2 RangeError: Invalid typed array length: undefined  
at new Int8Array ()  
at Y (29.bd0d951c.chunk.js:2:66586)  
at 29.bd0d951c.chunk.js:2:67165  
at Object.9904 (29.bd0d951c.chunk.js:2:2689361)  
at n (main.b6718321.js:2:137938)  
at Object.1829 (45.7f594e29.chunk.js:1:262)  
at n (main.b6718321.js:2:137938)  
at Module.2267 (279.c3c2ee58.chunk.js:1:130)  
at Function.n (main.b6718321.js:2:137938)  
si @ main.b6718321.js:2  
n.callback @ main.b6718321.js:2  
ha @ main.b6718321.js:2  
yi @ main.b6718321.js:2  
Ru @ main.b6718321.js:2  
t.unstable\_runWithPriority @ main.b6718321.js:2  
Ql @ main.b6718321.js:2  
zu @ main.b6718321.js:2  
bu @ main.b6718321.js:2  
(anonymous) @ main.b6718321.js:2  
t.unstable\_runWithPriority @ main.b6718321.js:2  
Ql @ main.b6718321.js:2  
Yl @ main.b6718321.js:2  
I @ main.b6718321.js:2  
w.port1.onmessage @ main.b6718321.js:2  
main.b6718321.js:2 Uncaught RangeError: Invalid typed array length: undefined  
at new Int8Array ()  
at Y (29.bd0d951c.chunk.js:2:66586)  
at 29.bd0d951c.chunk.js:2:67165  
at Object.9904 (29.bd0d951c.chunk.js:2:2689361)  
at n (main.b6718321.js:2:137938)  
at Object.1829 (45.7f594e29.chunk.js:1:262)  
at n (main.b6718321.js:2:137938)  
at Module.2267 (279.c3c2ee58.chunk.js:1:130)  
at Function.n (main.b6718321.js:2:137938)  
Y @ 29.bd0d951c.chunk.js:2  
(anonymous) @ 29.bd0d951c.chunk.js:2  
9904 @ 29.bd0d951c.chunk.js:2  
n @ main.b6718321.js:2  
1829 @ 45.7f594e29.chunk.js:1  
n @ main.b6718321.js:2  
2267 @ 279.c3c2ee58.chunk.js:1  
n @ main.b6718321.js:2  
DevTools failed to load source map: Could not load content for [https://viewer.imaging.datacommons.cancer.gov/slim/static/js/main.b6718321.js.map:](https://viewer.imaging.datacommons.cancer.gov/slim/static/js/main.b6718321.js.map:) Load canceled due to load timeout  
DevTools failed to load source map: Could not load content for [https://viewer.imaging.datacommons.cancer.gov/slim/static/js/45.7f594e29.chunk.js.map:](https://viewer.imaging.datacommons.cancer.gov/slim/static/js/45.7f594e29.chunk.js.map:) Load canceled due to load timeout  
DevTools failed to load source map: Could not load content for [https://viewer.imaging.datacommons.cancer.gov/slim/static/js/279.c3c2ee58.chunk.js.map:](https://viewer.imaging.datacommons.cancer.gov/slim/static/js/279.c3c2ee58.chunk.js.map:) Load canceled due to load timeout  
DevTools failed to load source map: Could not load content for [https://viewer.imaging.datacommons.cancer.gov/slim/static/js/29.bd0d951c.chunk.js.map:](https://viewer.imaging.datacommons.cancer.gov/slim/static/js/29.bd0d951c.chunk.js.map:) Load canceled due to load timeout  
DevTools failed to load source map: Could not load content for [https://viewer.imaging.datacommons.cancer.gov/slim/static/js/main.b6718321.js.map:](https://viewer.imaging.datacommons.cancer.gov/slim/static/js/main.b6718321.js.map:) Load canceled due to load timeout  
DevTools failed to load source map: Could not load content for [https://viewer.imaging.datacommons.cancer.gov/slim/static/css/279.0e207cc1.chunk.css.map:](https://viewer.imaging.datacommons.cancer.gov/slim/static/css/279.0e207cc1.chunk.css.map:) Load canceled due to load timeout  
DevTools failed to load source map: Could not load content for [https://viewer.imaging.datacommons.cancer.gov/slim/static/js/45.7f594e29.chunk.js.map:](https://viewer.imaging.datacommons.cancer.gov/slim/static/js/45.7f594e29.chunk.js.map:) Load canceled due to load timeout  
DevTools failed to load source map: Could not load content for [https://viewer.imaging.datacommons.cancer.gov/slim/static/js/29.bd0d951c.chunk.js.map:](https://viewer.imaging.datacommons.cancer.gov/slim/static/js/29.bd0d951c.chunk.js.map:) Load canceled due to load timeout

---

<div class="post-metadata">

**Author:** ![kirbyju](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/kirbyju/32/70_2.png) [@kirbyju](https://discourse.canceridc.dev/u/kirbyju)\
**Post date:** [June 3, 2022, 3:56pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/5 "2022-06-03T15:56:53Z")

</div>

Version 101.0.4951.67 (Official Build) (32-bit) is what I’m running, but just noticed it’s asking me to update.

---

<div class="post-metadata">

**Author:** ![kirbyju](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/kirbyju/32/70_2.png) [@kirbyju](https://discourse.canceridc.dev/u/kirbyju)\
**Post date:** [June 3, 2022, 4:00pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/6 "2022-06-03T16:00:26Z")

</div>

Same problem after updating to latest version on Windows. Also, I just noticed an option to use an app to open this page:

![image](https://us1.discourse-cdn.com/flex015/uploads/canceridc/original/1X/912daa34f7c3d8fa4cee67d98be08c41c46defa1.png)

That produces a blank screen in SLIM:

 ![image](https://us1.discourse-cdn.com/flex015/uploads/canceridc/original/1X/16330304dc07b4709eb6fe423fb33ba386b1b313.png)

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/fedorov/32/3_2.png) [@fedorov](https://discourse.canceridc.dev/u/fedorov)\
**Post date:** [June 3, 2022, 4:03pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/7 "2022-06-03T16:03:47Z")

</div>

@wlongabaugh do you have any comments?

I shared this with Markus, and asked him to join the forum.

@pgundluru can you please test if you can reproduce on Windows? I do not have access to Windows at the moment.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/fedorov/32/3_2.png) [@fedorov](https://discourse.canceridc.dev/u/fedorov)\
**Post date:** [June 3, 2022, 4:09pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/8 "2022-06-03T16:09:30Z")

</div>

@kirbyju I was kind of surprised your version is 32 bit (I didn’t realize they still exist!). I am not sure if this is the cause of the problem, but it might be. Can you try upgrading to a 64-bit version of Chrome (here’s one relevant article I quickly googled): [https://www.howtogeek.com/241501/you-should-upgrade-to-64-bit-chrome.-its-more-secure-stable-and-speedy/](https://www.howtogeek.com/241501/you-should-upgrade-to-64-bit-chrome.-its-more-secure-stable-and-speedy/).

---

<div class="post-metadata">

**Author:** ![kirbyju](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/kirbyju/32/70_2.png) [@kirbyju](https://discourse.canceridc.dev/u/kirbyju)\
**Post date:** [June 3, 2022, 4:32pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/9 "2022-06-03T16:32:26Z")

</div>

That’s amusing. I didn’t even notice since NIH pre-installs all of this stuff for us and I have to get an IT person to change anything. I’ll ask our helpdesk if they can install the 64 bit version for me.

---

<div class="post-metadata">

**Author:** ![hackermd](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@hackermd](https://discourse.canceridc.dev/u/hackermd)\
**Post date:** [June 3, 2022, 4:57pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/10 "2022-06-03T16:57:33Z")

</div>

This appears to be due to a server side error that results in a response with status code 404. We should take a look into the logs of the reverse proxy server.

We may also need to revisit the error handling of Slim and see whether we could further improve it, for example by retrying in case of a 404 error.

---

<div class="post-metadata">

**Author:** ![hackermd](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@hackermd](https://discourse.canceridc.dev/u/hackermd)\
**Post date:** [June 3, 2022, 4:59pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/11 "2022-06-03T16:59:36Z")

</div>

@kirbyju I am not sure why you get a blank screen via the Windows app. That is strange. Do you have a way to inspect the JavaScript console?

---

<div class="post-metadata">

**Author:** ![pgundluru1](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/pgundluru1/32/182_2.png) [@pgundluru1](https://discourse.canceridc.dev/u/pgundluru1)\
**Post date:** [June 3, 2022, 5:19pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/12 "2022-06-03T17:19:40Z")

</div>

@fedorov I am able to open up CPTAC Pathology images on a chrome browser including the one from the link shared.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/fedorov/32/3_2.png) [@fedorov](https://discourse.canceridc.dev/u/fedorov)\
**Post date:** [June 3, 2022, 7:04pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/13 "2022-06-03T19:04:37Z")

</div>

> [@pgundluru1](#):
>
> @fedorov I am able to open up CPTAC Pathology images on a chrome browser including the one from the link shared.

Can you test it on a 32 bit version of Chrome?

---

<div class="post-metadata">

**Author:** ![wlongabaugh](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/wlongabaugh/32/34_2.png) [@wlongabaugh](https://discourse.canceridc.dev/u/wlongabaugh)\
**Post date:** [June 3, 2022, 7:19pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/14 "2022-06-03T19:19:16Z")

</div>

I doubt this is a server side issue. The stack trace coming from the client-side code report “RangeError: Invalid typed array length: undefined” which (this is a hunch) suggests it is related to the inability to correctly handle an array that might be too large for a 32 bit system.

---

<div class="post-metadata">

**Author:** ![wlongabaugh](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/wlongabaugh/32/34_2.png) [@wlongabaugh](https://discourse.canceridc.dev/u/wlongabaugh)\
**Post date:** [June 3, 2022, 7:24pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/15 "2022-06-03T19:24:37Z")

</div>

I will note that while client side retry logic should _absolutely_ be implemented to handle 500 (server) errors, in the case of 400 (client) errors, it should make no difference.

---

<div class="post-metadata">

**Author:** ![wlongabaugh](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/wlongabaugh/32/34_2.png) [@wlongabaugh](https://discourse.canceridc.dev/u/wlongabaugh)\
**Post date:** [June 3, 2022, 7:27pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/16 "2022-06-03T19:27:40Z")

</div>

Note that this page specifically states (at least for Firefox, but I’m guessing it is universal) that RangeErrors are very much tied to 32-bit vs 64-bit systems:

> **[RangeError: invalid array length - JavaScript | MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/Invalid_array_length)**
>
> The JavaScript exception "Invalid array length" occurs when specifying an array length that is either negative, a floating number or exceeds the maximum supported by the platform (i.e. when creating an Array or ArrayBuffer, or when setting the...

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/fedorov/32/3_2.png) [@fedorov](https://discourse.canceridc.dev/u/fedorov)\
**Post date:** [June 3, 2022, 7:31pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/17 "2022-06-03T19:31:16Z")

</div>

> [@wlongabaugh](#):
>
> I will note that while client side retry logic should _absolutely_ be implemented to handle 500 (server) errors, in the case of 400 (client) errors, it should make no difference.

I captured this in [Handle web server errors · Issue #106 · ImagingDataCommons/slim · GitHub](https://github.com/herrmannlab/slim/issues/106)

---

<div class="post-metadata">

**Author:** ![wlongabaugh](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/wlongabaugh/32/34_2.png) [@wlongabaugh](https://discourse.canceridc.dev/u/wlongabaugh)\
**Post date:** [June 3, 2022, 7:31pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/18 "2022-06-03T19:31:30Z")

</div>

Perhaps Slim should detect what type of platform it is running on (32- or 64-bit) and print a message that it is only supported on the latter.

---

<div class="post-metadata">

**Author:** ![kirbyju](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.canceridc.dev/kirbyju/32/70_2.png) [@kirbyju](https://discourse.canceridc.dev/u/kirbyju)\
**Post date:** [June 3, 2022, 8:16pm UTC](https://discourse.canceridc.dev/t/cant-visualize-cptac-pathology-image/281/19 "2022-06-03T20:16:46Z")

</div>

My IT guy just installed 64bit and it’s working now. Thanks for your help!