Use web workers to avoid blocking the main UI thread during MSI processing #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Large MSI files and LZX-compressed files cause the browser to hang with "page unresponsive" warnings during parsing and extraction.
Changes
Architecture: Moved all Pyodide operations to a dedicated web worker thread
msi_viewer_worker.js: New worker handling Pyodide initialization, MSI parsing, and file extractionmsi_viewer.js: Refactored to communicate with worker via postMessage, handle UI updates onlymsi_viewer.md: Enhanced CSS with animated loading spinner and error statesProgress feedback: Added visual indicators for background operations
Resilience: Exponential backoff retry logic with timeout protection
Security: Input validation and safe variable passing
pyodide.globals.set()instead of string interpolationMemory management: Timeout cleanup prevents leak accumulation
Screenshot
The UI now remains responsive during all MSI operations, with clear visual feedback showing current processing status.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.