title: UITableView DequeueReusableCell sometimes creates new items despite already created more than items on screen, reusing "only" cca 80-95% times
body: <p>I have a UITableView with different cell types. For one type(smallest, I have different Height from 40 to like 1000px), only a few items are in queue and when scrolling up/down these few (typically 5) are reused and some (2-3) are created new ones.</p>
  
  <p>What is unpleasant is, that these cells takes a lot of memory (drawn by SkiaSharp - SKCanvasView) and for every scroll up/down 2-3 are created new ones, the old ones are not being destroyed/Disposed. (Using only WeakReference, etc.. but still I don't know why).</p>
  
  <p>So I I have a table with 300 items, after 100x scrollings up/down, I have created like 205 objects, causing memory leak.</p>
  
  <p>I would call Dispose on them, If I would know that UITableView is not going to reuse cell, but I suppose there is no such event.</p>
  
  <p>What is the best approach to solve this memory leak? How big is UITableView reuse queue? I suppose that problem is, that reuse queue is full, UITableView doesn't want to keep more items in queue and discards them. But Xamarin keeps them in RAM.</p>
  
  <p>On Android I have recycler view, I know about PoolSize for every item, I have an event when item is going to be recycled etc...</p>