Databases
StackOverflow2013
Postsdbo
PO[UIViewController hash]: message sent to deallocated instance with ARC
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO[UIViewController hash]: message sent to deallocated instance with ARC
    primarykey
    data
    text
    <p>Can't work this out, [UIViewController hash] is being sent to a view controller which has been rightly deallocated, it was pushed onto a navigation and then subsequently popped, then at some random point later this happens. Looks like the UIViewController class has some kind of static collection of view controllers where a reference to the old controller is still being held despite being deleted. </p> <pre><code> 206, stop reason = EXC_BREAKPOINT (code=EXC_I386_BPT, subcode=0x0) frame #0: 0x0225cdee CoreFoundation`___forwarding___ + 206 frame #1: 0x0225ccb2 CoreFoundation`_CF_forwarding_prep_0 + 50 frame #2: 0x017e1cd1 Foundation`objectHash + 33 frame #3: 0x017e3444 Foundation`hashProbe + 47 frame #4: 0x017f5d03 Foundation`-[NSConcreteHashTable hashGrow] + 217 frame #5: 0x017e3407 Foundation`-[NSConcreteHashTable addObject:] + 136 frame #6: 0x00f98089 UIKit`+[UIViewController setViewController:forView:] + 101 frame #7: 0x00f94c71 UIKit`-[UIViewController setView:] + 542 frame #8: 0x017ecf30 Foundation`_NSSetUsingKeyValueSetter + 77 frame #9: 0x017ecedb Foundation`-[NSObject(NSKeyValueCoding) setValue:forKey:] + 287 frame #10: 0x01807d50 Foundation`-[NSObject(NSKeyValueCoding) setValue:forKeyPath:] + 393 frame #11: 0x010ef71a UIKit`-[UIRuntimeOutletConnection connect] + 106 frame #12: 0x022f7dea CoreFoundation`-[NSObject performSelector:] + 58 frame #13: 0x022617f1 CoreFoundation`-[NSArray makeObjectsPerformSelector:] + 273 frame #14: 0x010ee26e UIKit`-[UINib instantiateWithOwner:options:] + 1178 frame #15: 0x00f941fc UIKit`-[UIViewController _loadViewFromNibNamed:bundle:] + 286 frame #16: 0x00f94779 UIKit`-[UIViewController loadView] + 302 </code></pre> <p>It looks like the private method [UIViewController setViewController:forView:], called from [UIViewController setView:] stores every view controller in a class level dictionary of view -> view controller perhaps. And at some point later whilst adding another VC to the collection, it needs to grow, this causes all the values to be rehashed in the collection, causing the [UIViewController hash] call to the delloced VC. Now question is why is the VC ref still in there? Maybe its because the view is still alive somehow without it's controller delegate.</p> <p>UPDATE: I can confirm that the view controller's view is still alive after the VC has been popped despite the VC being destroyed. Not quite sure why though.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USnbransby
    1. USnbransby
    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. VO
      singulars
      1. PO[UIViewController hash]: message sent to deallocated instance with ARC
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO[UIViewController hash]: message sent to deallocated instance with ARC
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPlace your code here or release memory by yourself instead of ARC
      singulars
      1. PO[UIViewController hash]: message sent to deallocated instance with ARC
      1. USGargo
    2. COThere is too much code to place here, also why would I want to release the memory myself?
      singulars
      1. PO[UIViewController hash]: message sent to deallocated instance with ARC
      1. USnbransby
    3. COThere's too little code here for anyone to provide much help.
      singulars
      1. PO[UIViewController hash]: message sent to deallocated instance with ARC
      1. USStephen Darlington
 

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