Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Are you running this code on a device or on the simulator? The simulator gives a bunch of false leaks (such as in AudioToolbox, CoreVideo, etc.). Also, the simulator seems to cache the <strong>entire</strong> video and not release it properly whereas the device buffers only what it needs along the way.</p> <p>I tested your code on the simulator with an mp4 video and I had similar results to what you were saying (10 live objects each time a video was played, with none dying... 20mb allocated, and 5mb left even after releasing). The living objects and memory allocation would keep growing and growing on the simulator.</p> <p>However, on my iPhone (with a 20mb video) it only allocated 900kb of memory total for the app, with no appreciable change when starting/stopping/releasing the video. It always stayed right around 900kb for the 10 times I tested it (starting/stopping/releasing). </p> <p>Looks like just another time you can't trust the simulator.</p> <p>The code I was testing with:</p> <pre><code>NSURL *url = [NSURL fileURLWithPath:[[NSBundle mainBundle] pathForResource:@"SomeMovieFile" ofType:@"mp4"]]; MPMoviePlayerController *newPlayer = [[MPMoviePlayerController alloc] initWithContentURL:url]; self.player = newPlayer; [newPlayer release]; [self.view addSubview:player.view]; // for my example, I didn't set the frame location, but no difference that would do [player play]; </code></pre> <p>Then in another button I stopped it and released the player:</p> <pre><code>[player.view removeFromSuperview]; player.initialPlaybackTime = -1; [player stop]; self.player = nil; // this is just a habit of mine.. calling stop should unload the buffers though [player release]; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POMPMoviePlayerController still leaking
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USiwasrobbed
    1. USiwasrobbed
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COYou should actually avoid the "player=nil; [player release];" because you are technically releasing "nil", *not* the allocated player, which could potentially cause a leak.
      singulars
      1. PO
      1. USpop850
    2. COActually, setting the object to nil will release the old value of the object and then set the object value to nil. Just like with any other object though, you still have to release anything you explicitly `alloc` / `init`.. I think you are getting confused with only setting an object to nil and then not releasing it. In that scenario, you are leaking the object since you still have a pointer to some object in memory that never gets deallocated.
      singulars
      1. PO
      1. USiwasrobbed
    3. COAcutally this code it's tested on an iPad, and the memory allocation has never been release completely. Anyway, if you tested the code you posted and you din't had any memory leaks it's courious, You set to nil the pointer before release the object.
      singulars
      1. PO
      1. USCesar
 

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