Mailing-List: contact dev-help@weex.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@weex.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAL2oOLeMcgyMjOefF2AZLLQtuJX1vdHrA9rTKh0nE2UqZJcRLw@mail.gmail.com>
References: <CAL2oOLeMcgyMjOefF2AZLLQtuJX1vdHrA9rTKh0nE2UqZJcRLw@mail.gmail.com>
From: shihan zheng <zhengshihan918@gmail.com>
Date: Mon, 4 Sep 2017 20:56:28 +0800
Message-ID: <CAB6Rc0aF0zFmyqSfUfi7kCYJz=Fpr2MUN0sn8yaGavDp_OuNVw@mail.gmail.com>
Subject: Re: Android memory holding in complex layout
To: dev@weex.incubator.apache.org
Content-Type: multipart/alternative; boundary="f403043664a6687a0605585ca52f"
archived-at: Mon, 04 Sep 2017 12:57:09 -0000

--f403043664a6687a0605585ca52f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, Chris:
    Thank you for your feedback . As you know=EF=BC=8CWeex needs  to save t=
he Dom
tree to re-render the native view when scrolling up and down =EF=BC=9B
We can easily reuse native view because of saving the Dom tree. As you
suggest,  serializing the Dom tree to sdcard  may cause
the scroll be not smooth, and it may be worse user experience.
    In your case, I suggest you can optimize to reuse the item  in DSL=EF=
=BC=8Cjust
like HTML5 ' best practice of endless page;
    we will continue to research the best solution to resolve this problem,
And if you have better idea , welcome to  tell to us immediately .

thank you !

2017-09-04 12:24 GMT+08:00 chris chu <chaxiu1@gmail.com>:

> Hi, Weex Team:
>
>     On Android, I found my Java heap kept growing(from 50MB to 120MB),
> when I scroll a complex layout in "WXListComponent". In this weex page, i=
t
> contains about hundreds of list items, and ten components in each list
> item, including image component. The Java Heap memory won't go down to 50=
MB
> until I close weex page.
>     Then I dumped Java heap when it was 120MB. It turns out that:
>     There are 217874 object which are belong to com.taobao.weex in Java
> Heap, Shallow Size is 14436604, Retained Size is 70853332.
>     There are 15808 WXDomObject, Shallow Size is 1644032, Retained Size i=
s
> 11075192.
>
>      I understand how Weex work, and in some way, this memory holding is
> inevitable. I just wonder if Weex Team will optimize this performance iss=
ue
> in Android.
>      Such as: Caching Dom Tree in sd card, or doing reusing work in Dom
> Layer like RecyclerView (only native view reuse is not good enough).
>
>
>
> =E2=80=8B
>
>      =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> My Environment is:
> Mac OS 10.12.5
> Android Studio 2.3, Gradle 2.3.3 / Android Studio 3.0 beta, Gradle 3.0
> =E2=80=8BNexus 6 Plus
> Android 7.1.2
> weex sdk: 0.11.0
>
>       Sincerely Chris.
>
>


--=20

Best Regards!
---------------------
Shihan Zheng (Weex project team member )

--f403043664a6687a0605585ca52f--