Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Enabling useCPURendering breaks the app #4564

Open
Omid-Heydarzadeh opened this issue Dec 2, 2024 · 0 comments
Open

[Bug] Enabling useCPURendering breaks the app #4564

Omid-Heydarzadeh opened this issue Dec 2, 2024 · 0 comments
Assignees
Labels
Awaiting Reproduction Can we reproduce the reported bug?

Comments

@Omid-Heydarzadeh
Copy link

Describe the Bug

Enabling useCPURendering in app config file breaks the app
Also, when it is enabled, cornerstone will still logs "using GPU rendering" in the console.
This issue is relevant to OHIF v3.8.5, v3.9.1 and v3.10.0-beta.12

Steps to Reproduce

  1. add useCPURendering: true to the app config (e.g. platform/app/public/config/default.js)
  2. run yarn dev
  3. open any of studies using basic viewer

The current behavior

This error shows up:

Context: Route /viewer
Error Message: Cannot destructure property 'direction' of 'metadata' as it is undefined.
Stack: TypeError: Cannot destructure property 'direction' of 'metadata' as it is undefined.
at StackViewport.getCameraCPU (http://localhost:3000/app.js:2623:17)
at evaluate (http://localhost:3000/extensions_cornerstone_src_index_tsx.js:5012:31)
at http://localhost:3000/app.js:134721:55
at Array.map ()
at props.evaluate (http://localhost:3000/app.js:134721:38)
at evaluateButtonProps (http://localhost:3000/app.js:134926:43)
at http://localhost:3000/app.js:134978:48
at Array.map ()
at http://localhost:3000/app.js:134978:36
at Array.reduce ()

The expected behavior

OHIF should load and view selected study instance correctly using CPU renderer.

OS

Windows 11 Enterprise 23H2

Node version

20.11.1

Browser

Chrome 131.0.6778.86, Firefox 133

@Omid-Heydarzadeh Omid-Heydarzadeh added the Awaiting Reproduction Can we reproduce the reported bug? label Dec 2, 2024
@sedghi sedghi self-assigned this Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Reproduction Can we reproduce the reported bug?
Projects
None yet
Development

No branches or pull requests

2 participants