It is indeed possible if you keep loading, but it is difficult for human operations to reach the point where it overflows. When there is a lot of data, the operation will start to get stuck. At that time, it will be harder for you to scroll down and continue loading. Also, maybe someone has limited the function, loading up to 1,000 items, and 1,000 items is enough for you to play.
Generally speaking, if it is simple text information, user information, ID, etc., it is more difficult to have memory overflow problems, unless you slide for a long, long, long, long time. The key is the image. Bitmap uses a loader to control the memory and automatically recycle it. This is the main cause of OOM.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It is indeed possible if you keep loading, but it is difficult for human operations to reach the point where it overflows. When there is a lot of data, the operation will start to get stuck. At that time, it will be harder for you to scroll down and continue loading. Also, maybe someone has limited the function, loading up to 1,000 items, and 1,000 items is enough for you to play.
Calling list.clear(); method after each slide can release memory
Generally speaking, if it is simple text information, user information, ID, etc., it is more difficult to have memory overflow problems, unless you slide for a long, long, long, long time.
The key is the image. Bitmap uses a loader to control the memory and automatically recycle it. This is the main cause of OOM.
By the way, the Android version of Sina Weibo is mainly packaged by the web interface
View recycling, overflow is unlikely.