日韩性视频-久久久蜜桃-www中文字幕-在线中文字幕av-亚洲欧美一区二区三区四区-撸久久-香蕉视频一区-久久无码精品丰满人妻-国产高潮av-激情福利社-日韩av网址大全-国产精品久久999-日本五十路在线-性欧美在线-久久99精品波多结衣一区-男女午夜免费视频-黑人极品ⅴideos精品欧美棵-人人妻人人澡人人爽精品欧美一区-日韩一区在线看-欧美a级在线免费观看

歡迎訪問 生活随笔!

生活随笔

當前位置: 首頁 > 人文社科 > 生活经验 >内容正文

生活经验

Android 你知道界面布局嵌套多少层之后会Crash吗

發布時間:2023/11/27 生活经验 25 豆豆
生活随笔 收集整理的這篇文章主要介紹了 Android 你知道界面布局嵌套多少层之后会Crash吗 小編覺得挺不錯的,現在分享給大家,幫大家做個參考.

我們先放一張Hierarchy?Viewer的圖:(模擬器Android4.4)

?

看到數字6了嗎,那個RelativeLayout是MainActivity的根ViewGroup,?而在RelativeLayout之前還有5層,?即系統默認的界面DecorView(FrameLayout) --> LinearLayout --> FramelLayout-- >ActionBarOverlayLayout --> ContentFrameLayout.

?直接說結果吧,用模擬器在API19? 也就是Android4.4?上最大可以嵌套39層,包含系統默認的5層,也就說我們最大可以寫34層的嵌套。

當嵌套層數達到40層時報如下異常,

10-27 11:38:53.901 25582-25582/com.aquarius.customview E/AndroidRuntime: FATAL EXCEPTION: mainProcess: com.aquarius.customview, PID: 25582java.lang.StackOverflowErrorat android.util.Pools$SynchronizedPool.acquire(Pools.java:154)at android.view.GLES20RecordingCanvas.obtain(GLES20RecordingCanvas.java:43)at android.view.GLES20DisplayList.start(GLES20DisplayList.java:61)at android.view.View.getDisplayList(View.java:13323)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2940)at android.view.View.getDisplayList(View.java:13357)at android.view.View.getDisplayList(View.java:13404)at android.view.View.draw(View.java:14182)at android.view.ViewGroup.drawChild(ViewGroup.java:3103)at android.view.View
View Code


在API23?Android6.0上嵌套層數可以更多,實驗了四十多層還依舊沒有crash

至于具體低于4.4的版本是什么樣的結果,我并沒有測試,且Android開源各大手機廠商可能會修改邏輯。不過考慮到向下兼容的問題,還是不應該嵌套太多層數,

當自己寫的布局層級超過10層的時候就該考慮優化布局了,因為即使應用不因為嵌套的太多而crash,也會造成渲染時間過長等問題,影響UI流暢度。

?

轉載于:https://www.cnblogs.com/sphere/p/7745687.html

總結

以上是生活随笔為你收集整理的Android 你知道界面布局嵌套多少层之后会Crash吗的全部內容,希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯,歡迎將生活随笔推薦給好友。