Switching between sibling routes results in the scope not being destroyed in ngRoute

[smhc]

The same issue as reported to ui-router also exists in ngRoute: angular-ui/ui-router#1766

The scope for the landing route is retained in the heap even when that state is navigated away. See the below for an example:

http://plnkr.co/edit/tS1z9PgWM927a3joiC95

Navigate to route B, then perform a heap snapshot. Both SibAObject and SibBObject will be on the heap. However, landing on '/home' first, then navigating between /home/a and /home/b allow the scopes to be dereferenced and freed correctly.

[smhc]

I've dug up this unresolved issue which appears similar: #3543

That old issue is apparently IE9 specific. However this new issue affects modern browsers (confirmed in chrome at least). Despite that, the reproduction code for the two issues is very similar.

[smhc]

Good news - this appears fixed in angular 1.4. Or at least, the reproduction code above no longer reproduces the problem when modified to use 1.4.

The fix appears to have come in on v1.3.15, most likely from the changes under issue: #11173