-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Editor: App becomes unresponsive when loading large posts #8628
Comments
To test this, I created a Gutenberg post (on the web, with Gutenberg demo content - a variety of blocks) with about 10,000 words and just that much content triggered the ANR dialog trying to open the post in Gutenberg in the app. |
Tested and confirmed using Pixel 3, Android 9, WPAndroid alpha-153 (11.9 alpha) on a self-hosted site running WP 5.1 and Gutenberg 5.1.1. Reported at wordpress-mobile/gutenberg-mobile#672. |
Adding some links to sample data which can be used for testing large posts:
|
Could not recreate this in either master or develop. Tried both in emulator and on my Pixel 3. |
This came up again in another user report and here are the steps to reproduce I came up with after reading their case:
I think the large number of images are the culprit in this case. (internal references: p4a5px-2om-p2/#comment-9755 and 1953510-zen) |
I think you're absolutely right and there isn't anything we can do right now. Aztec was designed this way and loading big posts will always be slow. We must hope that moving to Gutenberg and refactoring of the EditPostActivity (which will start soon) will help with this problem. |
I copied each of the writing samples Sheri listed in this comment to a new post on my test site. I then opened them in the app and had the following results when attempting to edit each post:
The above was tested on a Pixel 5, Android version 11, and version alpha-285 of the WordPress app. I also found the following relevant issues open in the Gutenberg Mobile repository: wordpress-mobile/gutenberg-mobile#2628, wordpress-mobile/gutenberg-mobile#1888 Leaving this issue open as I was able to replicate the app becoming unresponsive in the third example. |
cc-ing @hypest to get a second opinion on closing this in favour of the two related reports I linked to from the Gutenberg Mobile repository. I think they overlap well with the issue I was able to reproduce but I may be missing a case for keeping this one open. |
Thanks for checking the current status of this ticket @SiobhyB !
Just to be sure, did you try a converted-to-blocks version of that content or perhaps only copy pasted that content in Gutenberg's code editor? If the latter, the editor that will open up in native will be Aztec which indeed takes time and freezes the UI upon loading. But, gutenberg-mobile won't actually freeze the UI. Here's the test post I tried on my test site, after converting to blocks. In my testing on an Android 11 Pixel 2XL, the editor loads instantly, the UI is responsive (example: the 3-dot menu in the top right), although the content itself does take its time to load (~41secs). Can you try again? If you still find the app unresponsive then we should keep this ticket open, otherwise let's close it. |
Thanks @hypest, I can confirm I'd copied/pasted that particular post into a classic editor block. 🤦♀️ It all works as you outlined if I convert to blocks then try loading the editor again. All the other posts were tested within the editor's converted-to-blocks version. I'll go ahead to close this issue for now, given that we won't be focusing efforts on the classic editor going forward. |
A user reports that the app brings up a black screen and becomes unresponsive (shows “Application Not Responding (ANR)” error dialog) when loading large posts. The post does eventually load in the editor after choosing to wait.
In the reported case, the word count for the post is about 20,500 words (400 kb of content) and has a large amount of HTML. I tested with a post that has about 30,000 words (400 kb of content) and reproduced the black screen briefly, but no ANR error dialog. It's possible that the ANR is related to Aztec processing the HTML in the post, as well as the text content.
We should keep an eye on how Gutenberg performs with posts like this.
Internal ref: p4a5px-2iV-p2
The text was updated successfully, but these errors were encountered: