-
Notifications
You must be signed in to change notification settings - Fork 11
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
Intermittent work / fail behavior of OCP CAD Viewer #110
Comments
I found one problem that could be related to it. The viewer tries to respond to a resize window event and call The fix is to check whether |
I've published v2.5.0 which fixes the potential race condition. Could you please test it, @WayneSherman, since I can't reproduce it |
I testet a fresh install (windows OS) and the hanging empty viewer window on first start remained. I will make a seperate issue in the following days. |
@CePeU Yes please, since there was no issue open I forgot to deal with it |
Thanks for the updates. I tested v2.5.0 and the behavior is unchanged. When I "Open Folder..." with the demo file folder, most often the viewer window does not display properly. When I "Open File..." with the demo file, the viewer window usually displays correctly. |
I have no idea how to reproduce this |
Using
code --install-extension ms-python.python
code --install-extension bernhard-42.ocp-cad-viewer # ver 2.4.1
After following the installation instructions, when opening the auto created demo file "ocp_vscode_demo.py" the viewer pane intermittently does not initialize properly.
It behaves like an initialization race condition. Changing the way I load the file changes the timing and the failure frequency, e.g. opening a folder (workspace) which contains the demo file vs opening the demo file directly. When opening a folder the viewer fails to initialize most of the time, whereas when opening the file directly the viewer pane works most of the time. But both cases have intermittent work/fail behavior.
My test system is on the slow side (running in VirtualBox) so it probably is exposing this race condition where a faster system would not see it.
Originally posted by @WayneSherman in #104
The text was updated successfully, but these errors were encountered: