Fix/xsup 76577/rasterize extract lightweight freeze - #45947
MosheEichler wants to merge 4 commits into
Conversation
… lightweight mode
🤖 AI-Powered Code Review AvailableYou can leverage AI-powered code review to assist with this PR! Available Commands:
|
Coverage Report
|
||||||||||||||||||||||||||||||
|
🤖 Analysis started. Please wait for results... |
🤖 AI Review DisclaimerThis review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause. |
marketplace-ai-reviewer
left a comment
There was a problem hiding this comment.
Hi there! Thanks for your contribution to the rasterize pack. The changes look great, but there is just a minor formatting tweak needed in the release notes to align with our entity styling guidelines. Great work on fixing the content extraction issue!
@MosheEichler please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.
Co-authored-by: Marketplace AI reviewer <svc-mp-ai-reviewer@paloaltonetworks.com>
|
Validate summary Verdict: PR can be force merged from validate perspective? ✅ |
🔍 AI Triage Report AvailableAn automated triage report has been generated for this pipeline. Status: 📋 Triage Report
|
Status
Related Issues
Description
In lightweight mode the memory guard froze the tab after every page load, which disables JavaScript execution and purges the V8 heap. rasterize-extract is the only rasterize type that runs JS in the page (Runtime.evaluate), so the freeze destroyed the execution context it was about to use — the command failed with Cannot find default execution context and returned no content.
Change: added a freeze_on_load flag (default True) to wait_for_page_load_with_memory_guard and navigate_to_path, and pass False from extract_text_content.
Must have