Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Lots of confusion here... let's see if this helps:</p> <blockquote> <p>What I can't understand is why the system is trying to message this controller even though it has been deallocated and is there a way to tell the system that the controller doesn't exist any longer.</p> </blockquote> <p>While deallocation destroys the instance of an object, it doesn't destroy the references to the instances. With Zombie detection enabled, deallocation causes the runtime to substitute a zombie for the instance. The zombie then detects and logs when it is messaged.</p> <p>The reason why this happens is because the object has been deallocated without also removing all references to the object from the application's object graph. In this case, it looks like the deallocated controller was never unset as the controller from the UIWindow instance.</p> <p>That is, <strong><em>the processing of the notification is a red herring</em></strong>. In that backtrace, the notification has already been delivered and UIWindow is in the midst of processing it. Thus, the problem is somewhere between the UIWindow and your application. Most likely, your object has been deallocated <em>before</em> being removed from the window as its controller or delegate.</p> <p>Before your program is truly done with an object -- before you send the last <code>-release</code> call that balances the last existing <code>-retain</code> your application caused or called -- you must make sure that all weak references to the object are destroyed. For example, if your object is the delegate of a UIWindow, make sure you set the delegate of the window to <code>nil</code> (or some other object) before sending that last <code>-release</code>.</p> <p>Now, in this case, it may also simply be that you have over-released the object. You might still need the object around, but an extra <code>-release</code> or <code>-autorelease</code> somewhere is causing it to be destroyed before you were done with it.</p>
    singulars
    1. This table or related slice is empty.
    1. POView Controller being sent a message even though it has been deallocated
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USbbum
    1. USbbum
    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. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe error doesn't occur immediately after the object has been deallocated but rather upon the second time the interface has been rotated. In other words, I rotate the interface from landscape to portrait, deallocate the controller, do stuff in portrait mode without any problems, then reorient the interface to landscape mode and then the error occurs.
      singulars
      1. PO
      1. USMichael Gaylord
    2. COWhen there are references to a deallocated object, a crash can happen whenever something tries to send it a message. In your case it's happening when the orientation changes.
      singulars
      1. PO
      1. USNSResponder
 

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