8000 Posthoc does not handle when workers crash (presents as infinite loading) · Issue #58 · ShortestPathLab/posthoc-app · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Posthoc does not handle when workers crash (presents as infinite loading) #58

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.

Sign up for GitHub

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

Jump to bottom
Open
spaaaacccee opened this issue Dec 6, 2024 · 1 comment
Open

Posthoc does not handle when workers crash (presents as infinite loading) #58

spaaaacccee opened this issue Dec 6, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@spaaaacccee
Copy link
Member

When a web worker crashes, the main thread does not get informed of this, and as such keeps waiting for the worker to return. This is problematic when loading traces cause the parser worker to crash. When a web worker crashes, this event should be handled by the main thread.
@dharabor dharabor added the bug Something isn't working label Apr 2, 2025
@dharabor
Copy link
Member
dharabor commented Apr 2, 2025

This or a very similar issue currently affects the StarCraft example, on Firefox. Steps to reproduce: after first load, disable all layers except "Walk". The app goes into an infinite"loading" state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dharabor @spaaaacccee
0