1. Find the source of the problem: Are there too many ajax requests and too many picture requests when loading the interface? 2. If it is a problem of too many requests, communicate with the H5 people and see if the loading requests can be delayed or divided Segment requests, don’t let the request volume suddenly increase
Webview doesn’t know how to recycle it, but the easiest way is to add android:largeHeap="true" android:hardwareAccelerated="true" in the application manifests.xml to increase the memory that can be used by the app
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
1. Find the source of the problem: Are there too many ajax requests and too many picture requests when loading the interface?
2. If it is a problem of too many requests, communicate with the H5 people and see if the loading requests can be delayed or divided Segment requests, don’t let the request volume suddenly increase
Webview doesn’t know how to recycle it, but the easiest way is to add
android:largeHeap="true"
android:hardwareAccelerated="true"
in the application manifests.xml to increase the memory that can be used by the app