Popover adds a new scope every time it opens

[sdesmond]

Every time a popover displays, it adds a new scope to the mix. After a while, this causes things to slow down dramatically, especially when those popovers display a lot of data in an already large application. I've seen the behavior using Batarang.

When the popover is opened, a new child scope is created. When it is closed, the scope remains. When it is opened again, a new child scope is created which is identical to the first. When it is closed again, both scopes remain, etc. etc.

http://plnkr.co/edit/toUlHDz4hOlgJTCUv4EQ?p=preview

Transfer the code from Plunker to a local machine to see it in action (there are a lot of other scopes in Plunker and I don't see it happening there).

Is it possible that the scopes don't get cleaned up only when Batarang is
open? I have heard that Batarang holds on to references to scopes.

On Thu Oct 30 2014 at 8:23:23 AM Spencer notifications@github.com wrote:

Every time a popover displays, it adds a new scope to the mix. After a
while, this causes things to slow down dramatically, especially when those
popovers display a lot of data in an already large application. I've seen
the behavior using Batarang.

When the popover is opened, a new child scope is created. When it is
closed, the scope remains. When it is opened again, a new child scope is
created which is identical to the first. When it is closed again, both
scopes remain, etc. etc.

http://plnkr.co/edit/toUlHDz4hOlgJTCUv4EQ?p=preview

Transfer the code from Plunker to a local machine to see it in action
(there are a lot of other scopes in Plunker and I don't see it happening
there).

—
Reply to this email directly or view it on GitHub
#2907.

[sdesmond]

How would I be able to check that? Also, I've tested it with the Angular Strap version of Popover and I don't see the multiple scopes.

On Thu Oct 30 2014 at 11:29:31 AM redab notifications@github.com wrote:

Is it possible that the scopes don't get cleaned up only when Batarang is
open? I have heard that Batarang holds on to references to scopes.

On Thu Oct 30 2014 at 8:23:23 AM Spencer notifications@github.com
wrote:

Every time a popover displays, it adds a new scope to the mix. After a
while, this causes things to slow down dramatically, especially when
those
popovers display a lot of data in an already large application. I've
seen
the behavior using Batarang.

When the popover is opened, a new child scope is created. When it is
closed, the scope remains. When it is opened again, a new child scope is
created which is identical to the first. When it is closed again, both
scopes remain, etc. etc.

http://plnkr.co/edit/toUlHDz4hOlgJTCUv4EQ?p=preview

Transfer the code from Plunker to a local machine to see it in action
(there are a lot of other scopes in Plunker and I don't see it happening
there).

—
Reply to this email directly or view it on GitHub
#2907.

—
Reply to this email directly or view it on GitHub
#2907 (comment)
.

[chrisirhc]

This will be fixed via #2919 . Closing this as duplicate of #2709 .