You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to open a JSON file containing a single line with more than 300,000 columns, Phoenix becomes non-responsive. After force-closing Phoenix, subsequent launches automatically reopen the same large file, causing the IDE to freeze again and making it completely unusable.
Reproduction
Create or obtain a JSON file containing a single line with 300,000+ columns
Open Phoenix IDE
Open the large JSON file
Observe Phoenix becoming unresponsive
Force-close Phoenix
Attempt to reopen Phoenix IDE
Expected behavior
Phoenix should either:
Successfully open and handle large single-line JSON files
Gracefully warn users about file size limitations
Provide an option to prevent automatic reopening of problematic files from previous sessions
OS, Browser and Phoenix versions
Saw it in Linux ubuntu
logs or debug stack trace if any
No response
Additional context
This issue creates a feedback loop where Phoenix becomes unusable because it continuously attempts to reopen the problematic file on startup. The only current workaround is to manually delete Phoenix's session data to prevent it from reopening the file
The text was updated successfully, but these errors were encountered:
Describe the bug
When attempting to open a JSON file containing a single line with more than 300,000 columns, Phoenix becomes non-responsive. After force-closing Phoenix, subsequent launches automatically reopen the same large file, causing the IDE to freeze again and making it completely unusable.
Reproduction
Expected behavior
Phoenix should either:
OS, Browser and Phoenix versions
Saw it in Linux ubuntu
logs or debug stack trace if any
No response
Additional context
This issue creates a feedback loop where Phoenix becomes unusable because it continuously attempts to reopen the problematic file on startup. The only current workaround is to manually delete Phoenix's session data to prevent it from reopening the file
The text was updated successfully, but these errors were encountered: