Databases
StackOverflow2013
Postsdbo
POCATiledLayer large image crashing app
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCATiledLayer large image crashing app
    primarykey
    data
    text
    <p>This somewhat related to another post - but that one got kinda messed up - so I start from scratch:</p> <p>I have a CATiledLayer with a HUGE image in it (5780x6700px).</p> <p>The tiled layer is in a scrollview. When I start to scroll around, everything's fine up to a point where obviously too many tiles have been rendered. Then I get a memory warning and the app crashes.</p> <p>I tried to remove the tiledlayer from the view when I get the memory warning, clear it's contents (rootLayer.contents = nil AND tiledLayer.contents = nil) and then re-attach it empty to the view. didn't work...</p> <p>Would be thankful for any input...</p> <p><strong>Edit:</strong></p> <p>Thanks for the hints so far. Some of my assumptions seem to be wrong. I loaded the image in a function and then retained it - which is a contradiction to the CATiledLayer behaviour, I guess. Plus the <code>UIImage imageNamed:</code> seemed to cause some errors as well. Now I load the image in <code>drawLayer:(CALayer *) inContentext(CGContextRef) ctx</code> and use <code>UIImage imageWithContentsOfFile:</code> to load it.</p> <p>This seems to work without causing the memory to go low.</p> <p>However - the tiles are drawn painfully slow :(</p> <p>Here's my setup for the tiledLayer:</p> <pre><code>-(CATiledLayer *)initTiledLayers: (int)level{ //[tiledLayer release]; CGRect pageRect; CATiledLayer *myLayer = [CATiledLayer layer]; myLayer.delegate = self; if(level == 1){ pageRect = CGRectMake(0, 0, 690, 800); myLayer.tileSize = CGSizeMake(800, 800); myLayer.levelsOfDetail = 10; myLayer.levelsOfDetailBias = 2; }else if(level == 2){ pageRect = CGRectMake(0, 0, 1445, 1675); myLayer.tileSize = CGSizeMake(600, 600); myLayer.levelsOfDetail = 8; myLayer.levelsOfDetailBias = 2; }else if(level == 3){ pageRect = CGRectMake(0, 0, 2890, 3350); myLayer.tileSize = CGSizeMake(400, 400); myLayer.levelsOfDetail = 4; myLayer.levelsOfDetailBias = 1; }else if(level == 4){ pageRect = CGRectMake(0, 0, 5780, 6700); myLayer.tileSize = CGSizeMake(150, 150); myLayer.levelsOfDetail = 4; myLayer.levelsOfDetailBias = 0; } myLayer.frame = pageRect; return myLayer; [myLayer release]; } </code></pre> <p>(int)level indicates which image to be used (I'm switching images on certain zoom-levels). Level4 is the biggest image...</p> <p>And here's the drawLayer-function:</p> <pre><code>- (void)drawLayer:(CALayer *)layer inContext:(CGContextRef)ctx { CGContextSetRGBFillColor(ctx, 1.0, 1.0, 1.0, 1.0); CGContextFillRect(ctx, CGContextGetClipBoundingBox(ctx)); CGContextTranslateCTM(ctx, 0.0, layer.bounds.size.height); CGContextClearRect(ctx, CGRectMake(0,0,layer.bounds.size.width, layer.bounds.size.height)); CGContextScaleCTM(ctx, 1.0, -1.0); UIImage *map = [UIImage imageWithContentsOfFile: [[NSBundle mainBundle] pathForResource:[NSString stringWithFormat:@"Karte0%d", actLevel] ofType:@"jpg"]]; UIImage *wanderwege = [UIImage imageWithContentsOfFile: [[NSBundle mainBundle] pathForResource:[NSString stringWithFormat:@"Karte0%d_wanderwege", actLevel] ofType:@"png"]]; UIImage *rhb = [UIImage imageWithContentsOfFile: [[NSBundle mainBundle] pathForResource:[NSString stringWithFormat:@"Karte0%d_rhb", actLevel] ofType:@"png"]]; UIImage *abstecher = [UIImage imageWithContentsOfFile: [[NSBundle mainBundle] pathForResource:[NSString stringWithFormat:@"Karte0%d_abstecher", actLevel] ofType:@"png"]]; CGRect imageRect = CGRectMake (0.0, 0.0, map.size.width, map.size.height); CGContextDrawImage (ctx, imageRect, [map CGImage]); imageRect = CGRectMake (0.0, 0.0, wanderwege.size.width, wanderwege.size.height); CGContextDrawImage (ctx, imageRect, [wanderwege CGImage]); imageRect = CGRectMake (0.0, 0.0, rhb.size.width, rhb.size.height); CGContextDrawImage (ctx, imageRect, [rhb CGImage]); imageRect = CGRectMake (0.0, 0.0, abstecher.size.width, abstecher.size.height); CGContextDrawImage (ctx, imageRect, [abstecher CGImage]); } </code></pre> <p>Yeah - I know - I actually draw 4 images into the context. The PNGs are overlays which I need to dynamically add to the main-image...</p> <p>I tried to merge the images into one - but this seems to be even more mem/cpu-consuming ;)</p> <p>Any further help is greatly appreciated!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USUrs
    1. USUrs
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COCould you be a little more specific? What happens when you reset the contents and reattach it?
      singulars
      1. POCATiledLayer large image crashing app
      1. USSophie Alpert
    2. COhow are you loading the image? `UIImage imageNamed` has had some memory leak problems (really over caching I suspect, but anyway net effect is the same).
      singulars
      1. POCATiledLayer large image crashing app
      1. USDad
    3. CO@Ben: When I reattach the layer, it is black (aka emtpy, it seems). But after the first few tiles are drawn, the memory-warning comes back. I tried every tile size from very small to very big. I also set the LOD from like 2 to 100. The bias was set from like 0 to 2. @Dad - I do use UIImage imageNamed for loading - will give this a try (although, I'm not sure whether I tried this before :)
      singulars
      1. POCATiledLayer large image crashing app
      1. USUrs
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload