Databases
StackOverflow2013
Postsdbo
POCreating autoreleased object inside GLKViewController run loop causes malloc error
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCreating autoreleased object inside GLKViewController run loop causes malloc error
    primarykey
    data
    text
    <p>I'm currently using GLKit to do some OpenGL drawing. I created a normal UIViewController and then added a GLKViewController subclass inside a container to do my drawing. While everything runs fine initially, if I let my program run for a period of time (perhaps 15-30 minutes), eventually it crashes and gives me the following error.</p> <pre><code>malloc: *** mmap(size=2097152) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug </code></pre> <p>So I turned on the malloc_error_break breakpoint, and the stack trace points to the following code.</p> <pre><code>-(NSArray*)meshes:(NSArray *)meshes sortedFromFrontToBack:(BOOL)sortedFromFrontToBack { NSMutableArray *sortedMeshes = meshes.mutableCopy; [sortedMeshes sortUsingComparator:^NSComparisonResult(id obj1, id obj2) { DSNode *mesh1 = obj1; DSNode *mesh2 = obj2; GLKVector3 depth1 = isnan(mesh1.boundingSphere.radius) ? mesh1.transformationState.position : mesh1.boundingSphere.center; GLKVector3 depth2 = isnan(mesh2.boundingSphere.radius) ? mesh2.transformationState.position : mesh2.boundingSphere.center; GLKMatrix4 mesh1ToCameraSpace = [mesh1 nodeToOtherNodeTransform:self]; GLKMatrix4 mesh2ToCameraSpace = [mesh2 nodeToOtherNodeTransform:self]; GLKVector3 depth1InCameraSpace = GLKMatrix4MultiplyVector3WithTranslation(mesh1ToCameraSpace, depth1); GLKVector3 depth2InCameraSpace = GLKMatrix4MultiplyVector3WithTranslation(mesh2ToCameraSpace, depth2); NSNumber *n1 = [NSNumber numberWithFloat:depth1InCameraSpace.z]; NSNumber *n2 = [NSNumber numberWithFloat:depth2InCameraSpace.z]; /* Breakpoint triggered here */ if(sortedFromFrontToBack) { return [n2 compare:n1]; } return [n1 compare:n2]; }]; return sortedMeshes; } </code></pre> <p>As I commented, the [NSNumber numberWithFloat:] call throws the malloc error. This method gets called once each frame from my GLKViewController's drawInRect method. Essentially, I have a class which keeps track of my cameras and the meshes which are going to be drawn by OpenGL, and it sorts them in camera space from either front to back for opaque meshes or back to front for transparent before drawing them. </p> <pre><code>- (void)glkView:(GLKView *)view drawInRect:(CGRect)rect { glClearColor(self.clearColor.r, self.clearColor.g, self.clearColor.b, self.clearColor.a); glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT); DSDirector *director = [DSDirector sharedDirector]; for(DSMesh *mesh in director.opaqueMeshes) { [mesh draw]; } /* The director class keeps track of my scene's cameras and meshes and calls the above method to return the scene's transparent meshes properly sorted */ for(DSMesh *mesh in director.transparentMeshes) { [mesh draw]; } } </code></pre> <p>From what I've read, the autorelease pool should drain at the end of each run loop, so I wouldn't think that creating a bunch of autoreleased objects every frame is an issue, they should all get flushed each frame. I've profiled my program and checked for any leaks and can't find any, and I'm using ARC as well, which should minimize the risk. When I profile it, the live bytes total never budges, although the overall bytes rises quite quickly, and no leaks are found. In addition, didReceiveMemoryWarning never fires. I'm stumped.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDevin
    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
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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