volley內(nèi)存溢出的問題所在

volley內(nèi)存溢出的問題所在

　　在網(wǎng)絡(luò)請求中有網(wǎng)絡(luò)溢出現(xiàn)象，可能大家很少見到過這種情況，可為了解決這問題。為此學(xué)習(xí)啦小編為大家整理推薦了，希望大家喜歡。

　　volley內(nèi)存溢出

　　官網(wǎng)上有寫，然后創(chuàng)建RequestQueue 的時候用Application的context。If your application makes constant use of the network, it's probably most efficient to set up a single instance of RequestQueue that will last the lifetime of your app. You can achieve this in various ways. The recommended approach is to implement a singleton class that encapsulates RequestQueue and other Volley functionality. Another approach is to subclass Application and set up the RequestQueue in Application.onCreate(). But this approach is discouraged; a static singleton can provide the same functionality in a more modular way.

　　A key concept is that the RequestQueue must be instantiated with the Application context, not an Activity context. This ensures that the RequestQueue will last for the lifetime of your app, instead of being recreated every time the activity is recreated (for example, when the user rotates the device).

　　圖一：

　　圖二：