[Bug] Problem displaying some images in Chrome mobile

[abasb75]

Describe the Bug

hi,
I was updating to the cornerstone3D from old cornerstone, but I noticed that some images are not displayed in Chrome Mobile.

But this problem does not exist in Firefox.

i test in ohif viewer local and cornerstone live example (https://www.cornerstonejs.org/live-examples/local). They also have problems:

Steps to Reproduce

There is a problem in displaying the images of Dicom Android Chrome

The current behavior

There is a problem in displaying the images of Dicom Android Chrome

The expected behavior

There is a problem in displaying the images of Dicom Android Chrome

OS

android

Node version

20

Browser

chrome

[sedghi]

Hmm, I think Chrome on Android might have a bug. What Android phone are you using? We test our rendering on the Pixel 8.

[abasb75]

huawie p50 with latest version of chrome: snapdragon 888 with 8gb ram.

I have uploaded some images having this problem on cornerstone3D in the link below:
https://github.com/abasb75/dicom-parser/tree/main/test-dcm

Please check one or two of the images. all of image displayed on cornerstone v2 without any problem.

Can the problem be from vtk-js?

[sedghi]

Not sure really since firefox works. I don't have huawie p50, so i don't think i can debug this really

[abasb75]

i make an example for this issue. do you have not problem on your phone so can you see rendered image on mobile chrome?
https://abasb75.github.io/corenerstone-test-react-vite/

[daker]

Similar issue #1653 it's due to OES_texture_float_linear extension support missing in Chrome GPU driver on Huawei devices

[934556826]

I downgraded to cornerstone3D@^1.78.1, and it can render normally, but some very old models, such as Huawei mate9, still cannot render

[abasb75]

this is my console warning :
[.WebGL-0xd7ad6300]RENDER WARNING: texture bound to texture unit 0 is not renderable. It might be non-power-of-2 or have incompatible texture filtering (maybe)?

[abasb75]

it's seem problem is related to rescaleIntercept if has -1024 value. when i change this code :

image will render badly.

[Steven-DD]

I think you can try to see if this plugin is missing OES_texture_float，I saw a reply to this in the openlayers issues，I think you may be experiencing the same problem!

[abasb75]

I think you can try to see if this plugin is missing OES_texture_float，I saw a reply to this in the openlayers issues，I think you may be experiencing the same problem!

i check and

and OES_texture_float is avaible in p50 model

[Steven-DD]

https://webglreport.com
Are there any unsupported plugins in this list?

[Steven-DD]

Can you provide your Android version?
If this image works on other phones and GPU rendering modes, then the probability is that the problem is with WebGL support.

[abasb75]

image displayed in other webgl base viewer. for example meddream:

[Steven-DD]

If so, would trying to update the Android version solve the problem, the version shown in the test report seems to be Android 12

My guess is that the problem is probably a version compatibility issue, cornerstonejs may be using some poorly-compatible api, and there have also been problems with WebGL support on Android versions pointed out in other forums, with the problem occurring more often on the lower Android versions.

On meddream they may have a special way of handling it, apparently they have better support on older/lower version phones.

[sedghi]

You need to send the webgl 2 (notice 2.0) report, not 1

[abasb75]

OES_texture_float not avaibaled in webgl2. it is not related to device

[daker]

Try to see why it's not available by checking chrome://gpu adresse in chrome, maybe the extension is disabled for some reason

[abasb75]

Try to see why it's not available by checking chrome://gpu adresse in chrome, maybe the extension is disabled for some reason

i found reason of issue is not OES_texture_float supporting. probably, reason of issue is Max textturesize limit on chrome android that is 4096 but in firefox (android/pc) or chrome pc is 16384.

[sedghi]

4096 should we good enough for most data sizes, means the dimension in each direction should be less than 4096