appWidget process reused for update and eating memory
<ul>
<li><p>A simple appWidget would update itself in 30 mins minimum. Most of the times that time is enough for the "appWidget process" for being killed by the system. A new process starts at updates.</p></li>
<li><p>In my appWidget there are custom <code>intent-filters</code> and <code>broadcasts</code> (combinig with <code>AlarmManager</code>) to update it more frequently and the <strong>process is not getting killed but reused</strong> by the system when the update takes place. At every custom update, the appWidget runs a function that refreshes the <code>RemoteView</code> of the appWidget. That function modifies a <code>BitMap</code> and pushes it to the <code>view</code>.</p></li>
</ul>

<p>At every update a <code>BitMap</code> is being processed so whenever a custom, frequent update takes place, the reused process is getting bigger and bigger (about 1MB) in the memory.
Is this normal? Why is that?
How can I avoid this? So the update remains frequent but there won't be a process getting bigger and bigger. (Avoid reusing of the process or dunno.)</p>

<p>Also tested that if I comment out the contents of the update function (that leaves me an empty appWidget), the frequent, custom update wont eat the memory (but keeps the process alive and reused the same way as it was processing <code>BitMaps</code>, just processing nothing now and that's why it's keeping the size in memory I think). </p>

<p>Any suggestions? Is it a problem at all? I mean if it gets too big, the system will kill it eventually. But I dont't know if it is ok or not.</p>
