Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

"Paused in debugger" in Chrome with version "0.7.7" #638

Closed
fanshuai opened this issue Feb 14, 2017 · 14 comments · Fixed by #639
Closed

"Paused in debugger" in Chrome with version "0.7.7" #638

fanshuai opened this issue Feb 14, 2017 · 14 comments · Fixed by #639

Comments

@fanshuai
Copy link

2017-02-15 00 56 43

When I click a button with routerLink for change router url it raise, only with version 0.7.7.

@JiaLiPassion
Copy link
Collaborator

@fanshuai , thank you for reporting the issue, I will make a PR to remove it.

@rsnider19
Copy link

I am seeing the same thing when I run code in this.zone.runOutsideAngular(() => {...});. It is happening in 0.7.7, but not in 0.7.6. Even if you remove the debugger, it is still going to throw that error. Could there be another issue going on here?

@JiaLiPassion
Copy link
Collaborator

@rsnider19 , can you post a screenshot of the error or the pause on debugger?

@rsnider19
Copy link

rsnider19 commented Feb 19, 2017

I am using Zingchart and running it's render outside of Angular like they suggest. The reason is they frequently use setInterval and setTimeout for animations and you don't want the change detector triggered. If I don't run it outside of Angular, I am only getting the top error.

image

@JiaLiPassion
Copy link
Collaborator

@rsnider19 , thank you for the error screenshot, could you post a repository to reproduce so I can debug into it?

@rsnider19
Copy link

rsnider19 commented Feb 20, 2017

Sure thing! Here is a plunk. Just hover over the sections of the pie chart a couple times and it will trigger.
https://plnkr.co/edit/gar5B50EwAfrIrdU60m5

In UIDonutComp.ngAfterViewInit(), it only happens when data.tooltip.sticky is set to true, which keeps the tooltip showing for a brief moment. I assume they are using setInterval to do this.

JiaLiPassion added a commit to JiaLiPassion/zone.js that referenced this issue Feb 21, 2017
JiaLiPassion added a commit to JiaLiPassion/zone.js that referenced this issue Feb 21, 2017
@JiaLiPassion
Copy link
Collaborator

@rsnider19, Thank you, I have made a PR to fix this one.

JiaLiPassion added a commit to JiaLiPassion/zone.js that referenced this issue Feb 21, 2017
@rsnider19
Copy link

Awesome! Thanks!

@naveedahmed1
Copy link

Should this PR also fix the issues reported here angular/angular#14683 (comment)

@JiaLiPassion
Copy link
Collaborator

@naveedahmed1 , yes, the same issue.

@naveedahmed1
Copy link

@JiaLiPassion btw when should we expect it to be released?

@JiaLiPassion
Copy link
Collaborator

@naveedahmed1 , I think it is under review. It will take some time, Thank you.

@naveedahmed1
Copy link

Is it possible to use the version with your submitted pr while its under review?

@JiaLiPassion
Copy link
Collaborator

@naveedahmed1 , sure ,you can use the attached file to test.
zone.js.zip

mhevery pushed a commit that referenced this issue Mar 7, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants