Bug located in load state on linux
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 52/100
研究方向
Reproduce with visor-cli instance start, visor-cli instance load saved1, or deploy/docker/dev/docker-compose.yml, using the saved visor.json and cached dataset. Compare the isolated load_state path with the working add_dataset case; done means loading into an empty Linux or dev-container scene displays the dataset in the canvas without the std::bad_alloc exception.
由索引模型根據 Issue 內容生成。
描述
🐞 Description of the bug
When loading a state from an empty scene in a Linux environment, the visualizer gets into a broken state, not fixable by a refresh or a new API call.
The viewer does not display the new dataset in the canvas, though the UI elements are responsive and seem to contain the correct info (e.g. the tree view hierarchy and the part properties panel). A refresh does not restore the dataset in the canvas.
The uncaught exception message reads Exception {message: Array(2), stack: 'Error: std::bad_alloc,std::bad_alloc\n at ___thr…tkWebAssembly.wasm:wasm-function[37703]:0x1c82765'}
Notes:
- This behaviour works as expected on Windows. It shows the error behaviour on a Linux system, and on a Docker container on a Windows system.
- Was exposed when a regression test started failing, but upon further investigation that test seems to have been passing despite the canvas being empty on linux.
- The described behaviour on linux has been reproduced on linux tracing back to Mar 2026 (or further) in the old internal repo: e.g. on c34ebb92dbca1cb876612686194be22a92d848b2.
- The bug was found when running
load_stateinto an empty scene, which also loads a dataset. To make sure this doesn't also affectadd_dataset, tested runningadd_datasetfrom an empty scene on the VISOR main branch, in the python3.11 dev docker container. It succeeded. The bug is isolated toload_state.
📝 Steps to reproduce
Two options: Linux environment, or use the dev docker container (on any environment, e.g. Windows). The reproduction for both is the same, except that the way the service is run is different. The two options for running the service are outlined here; the reproduction is in the next section and is the same for both.
1. Running the VISOR service
a. Linux environment
> visor-cli server start
b. VISOR dev docker container
docker compose -f deploy/docker/dev/docker-compose.yml up --build
This will run the VISOR service on the same default port as the CLI command above.
2. Reproduction
a. Prerequisite: save a state from a VISOR scene.
> visor-cli instance start examples/assets/vtk_scene_sphere_l2_b3_r32_v3_c1_z0.vtm
# adjust camera/part properties etc>
> visor-cli instance save saved1
# directory saved1 contains the `visor.json` file and the cached dataset
b. Start a VISOR visualizer with an empty scene, and load the saved state
* visor-cli instance start
* visor-cli instance load saved1
📦 Installed packages and configuration
Tested on the following configurations:
- Windows with docker container
- Linux
🚦 Defines the severity of the bug. In the case of class-3, specific information must be added.
Class 1 - Crash/Major data loss
📦 Support ticket ID
No response
🐞 Found in
No response
🩹 Fixed in
No response
Root cause
No response
Third Party
- This bug is introduced by a third party
Released Bug
- This bug is in a released product
- 主要語言
- Python
- 星號
- 2
- 分支
- 1
- 平均合併
- 3 天 6 小時
- 30 天內合併 PR
- 29
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
ansys/Visual-Interactive-Simulation-Object-Renderer 的其他 Issue
-
Apply button未關閉enhancement
難度 2/5 1-3 小時 新手友好度 68/100
ansys/Visual-Interactive-Simulation-Object-Renderer#157 ·
維護者通常 1 天內回覆
-
visor-setup on macOS可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 1-3 小時 新手友好度 85/100
ansys/Visual-Interactive-Simulation-Object-Renderer#148 ·
維護者通常 1 天內回覆
-
technical
難度 4/5 3-5 天 新手友好度 48/100
ansys/Visual-Interactive-Simulation-Object-Renderer#164 ·
維護者通常 1 天內回覆
-
technical
難度 5/5 一週以上 新手友好度 35/100
ansys/Visual-Interactive-Simulation-Object-Renderer#163 ·
維護者通常 1 天內回覆
-
functional
難度 5/5 一週以上 新手友好度 20/100
ansys/Visual-Interactive-Simulation-Object-Renderer#160 ·
維護者通常 1 天內回覆
查看 ansys/Visual-Interactive-Simulation-Object-Renderer 的全部 Issue
相似的 Issue
-
comp/gateway comp/plugins duplicate P3 type/bug
難度 2/5 1-3 小時 新手友好度 82/100
NousResearch/hermes-agent#137019 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
bot-triaged module: docs triaged
難度 1/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
new-entry
難度 2/5 1-3 小時 新手友好度 78/100
BinWang28/audio-ai-hub#194 ·
-
confluence: a paged listing's links re-encode a parameter they carry, where real carries it as sent未關閉fidelity
難度 2/5 1-3 小時 新手友好度 63/100
維護者通常 1 天內回覆