IM running b4a 2.2 using httpUtils2 and the new http lib 1.22 and . My app is running fine except memory consumption is a bit high on low memory 16mb heap devices. In debugging using DDMS and eclipse memory analyzer(MAT) I noticed the following:
http, DefaultClientConnection was using 40%(2.3MB) of the heap
further investigation relevealed:
12 DefaultClientConnections
each connection with 174k assigned to the socketinputbuffer
The data stored in the buffers were successfull Http responses. But these were older(minutes) responses and were still lingering.
Question 1, is this a result of http connection pooling. I would have expected that consumeContent or equiv would have been called after a successful http response. If so why is the data still in memory minutes after?
http, DefaultClientConnection was using 40%(2.3MB) of the heap
further investigation relevealed:
12 DefaultClientConnections
each connection with 174k assigned to the socketinputbuffer
The data stored in the buffers were successfull Http responses. But these were older(minutes) responses and were still lingering.
Question 1, is this a result of http connection pooling. I would have expected that consumeContent or equiv would have been called after a successful http response. If so why is the data still in memory minutes after?
