You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@weex.apache.org by "codefurture (JIRA)" <ji...@apache.org> on 2018/04/04 11:15:00 UTC
[jira] [Commented] (WEEX-273) The application may be doing too much
work on its main thread
[ https://issues.apache.org/jira/browse/WEEX-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425343#comment-16425343 ]
codefurture commented on WEEX-273:
----------------------------------
when spa will lead too many views, when you change to page 2, remove page one node and state
> The application may be doing too much work on its main thread
> -------------------------------------------------------------
>
> Key: WEEX-273
> URL: https://issues.apache.org/jira/browse/WEEX-273
> Project: Weex
> Issue Type: Bug
> Components: Android
> Affects Versions: 0.18
> Environment: platform:android
> version:5.1.0
> weex version:0.18.0-beta-2
> Reporter: mjsornp
> Assignee: zhengshihan
> Priority: Critical
>
> our android platform operate step as below:
> # weex page（SPA mode, page 1） start anothor APK to scan QR code
> # another APK scan QR code and then finish()
> # weex onActivityResult invoke jsCallBack to show QR code content in weex page(SPA mode, page2)
> # The weex page2 sometimes display slow after another APK scan code Activity has finished.
>
> The android log show:
> Choreographer: Skipped 37 frames! The application may be doing too much work on its main thread.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)