https://bugzilla.wikimedia.org/show_bug.cgi?id=68845

            Bug ID: 68845
           Summary: Safari on iPad crashes when viewing large articles?
           Product: MobileFrontend
           Version: unspecified
          Hardware: Tablet PC
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Unprioritized
         Component: beta
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected]
       Web browser: ---
   Mobile Platform: ---

When viewing an article as large as
https://en.m.wikipedia.org/wiki/Fukushima_Daiichi_nuclear_disaster, when I
click one of the table of contents links, the screen turns white and my Safari
crashes. It may also crash my iPad as well. Is MobileFrontend using way too
much memory for large pages? It seems to be scrolling through the long page by
setting scrollTop to something else that is causing the crash. The iPad, I
think, is using a lot of memory when I view such a long page. I do not think it
is MobileFrontend's issue. It might just be providing safari some awful lot of
content that tells safari to use a hell of a lot of memory. It could also be
the images, have you set any custom fonts? You could also split the page into
sections so the user reads one section, clicks on a link that goes to the next
section to continue reading the article, if you guys cannot reproduce this. You
could also improve performance by loading content when the user scrolls down to
them, and removing content from the page when is not viewed for some time. Can
you check if this memory issue happens on the iPhone as well?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to