Weird rendering behavior on IE11 + Angular 1.5.11












7














We're currently developing an application in Angular version 1.5.11. It has become quite big now (hundreds of controllers etc.), and we stumbled upon an issue in Internet Explorer 11:



After some time (sometimes few minutes, sometimes few hours) the page starts to have rendering glitches - the letters are fading/disappearing/changing color. It also affects other tabs opened in the same window (screenshot from the Excel Online having the same issue). Also, there are no errors in console.



Did anyone come across similar issue? Also, "just using a normal browser" is not a viable option due to client's requirements.



Restarting the browser helps, but it's more of a workaround than an actual solution.





Application tab (it appears on every element of the page as well, cropped for visibiltity):
Application



Excel Online tab on the same browser:
Excel tab on the same browser










share|improve this question
























  • no error in console ?
    – federico scamuzzi
    Nov 19 '18 at 14:14










  • @federicoscamuzzi - nothing
    – Lemurr
    Nov 19 '18 at 14:15










  • Your fonts broke. Do you use custom fonts? Have you checked the Performance tab for any anomalies?
    – Aleksey Solovey
    Nov 19 '18 at 14:24










  • @AlekseySolovey - we use "Lato" font, opening performance tab on IE11 (or any of dev tools in that matter) is utterly slow and takes minutes to even open. We can check it next time we encounter this bug, but it also happens on other tabse as well. Is it possible that broken font can crash the rendering engine in the whole browser?
    – Lemurr
    Nov 19 '18 at 14:38






  • 1




    can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. Besides, I suggest you could try to use different computer or IE 11 version (you could try to upgrade the IE 11 to the latest version) to test your code to verify whether still meet this behavior.
    – Zhi Lv - MSFT
    Nov 20 '18 at 7:35


















7














We're currently developing an application in Angular version 1.5.11. It has become quite big now (hundreds of controllers etc.), and we stumbled upon an issue in Internet Explorer 11:



After some time (sometimes few minutes, sometimes few hours) the page starts to have rendering glitches - the letters are fading/disappearing/changing color. It also affects other tabs opened in the same window (screenshot from the Excel Online having the same issue). Also, there are no errors in console.



Did anyone come across similar issue? Also, "just using a normal browser" is not a viable option due to client's requirements.



Restarting the browser helps, but it's more of a workaround than an actual solution.





Application tab (it appears on every element of the page as well, cropped for visibiltity):
Application



Excel Online tab on the same browser:
Excel tab on the same browser










share|improve this question
























  • no error in console ?
    – federico scamuzzi
    Nov 19 '18 at 14:14










  • @federicoscamuzzi - nothing
    – Lemurr
    Nov 19 '18 at 14:15










  • Your fonts broke. Do you use custom fonts? Have you checked the Performance tab for any anomalies?
    – Aleksey Solovey
    Nov 19 '18 at 14:24










  • @AlekseySolovey - we use "Lato" font, opening performance tab on IE11 (or any of dev tools in that matter) is utterly slow and takes minutes to even open. We can check it next time we encounter this bug, but it also happens on other tabse as well. Is it possible that broken font can crash the rendering engine in the whole browser?
    – Lemurr
    Nov 19 '18 at 14:38






  • 1




    can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. Besides, I suggest you could try to use different computer or IE 11 version (you could try to upgrade the IE 11 to the latest version) to test your code to verify whether still meet this behavior.
    – Zhi Lv - MSFT
    Nov 20 '18 at 7:35
















7












7








7







We're currently developing an application in Angular version 1.5.11. It has become quite big now (hundreds of controllers etc.), and we stumbled upon an issue in Internet Explorer 11:



After some time (sometimes few minutes, sometimes few hours) the page starts to have rendering glitches - the letters are fading/disappearing/changing color. It also affects other tabs opened in the same window (screenshot from the Excel Online having the same issue). Also, there are no errors in console.



Did anyone come across similar issue? Also, "just using a normal browser" is not a viable option due to client's requirements.



Restarting the browser helps, but it's more of a workaround than an actual solution.





Application tab (it appears on every element of the page as well, cropped for visibiltity):
Application



Excel Online tab on the same browser:
Excel tab on the same browser










share|improve this question















We're currently developing an application in Angular version 1.5.11. It has become quite big now (hundreds of controllers etc.), and we stumbled upon an issue in Internet Explorer 11:



After some time (sometimes few minutes, sometimes few hours) the page starts to have rendering glitches - the letters are fading/disappearing/changing color. It also affects other tabs opened in the same window (screenshot from the Excel Online having the same issue). Also, there are no errors in console.



Did anyone come across similar issue? Also, "just using a normal browser" is not a viable option due to client's requirements.



Restarting the browser helps, but it's more of a workaround than an actual solution.





Application tab (it appears on every element of the page as well, cropped for visibiltity):
Application



Excel Online tab on the same browser:
Excel tab on the same browser







angularjs internet-explorer-11






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 19 '18 at 14:17

























asked Nov 19 '18 at 14:12









Lemurr

1,95941939




1,95941939












  • no error in console ?
    – federico scamuzzi
    Nov 19 '18 at 14:14










  • @federicoscamuzzi - nothing
    – Lemurr
    Nov 19 '18 at 14:15










  • Your fonts broke. Do you use custom fonts? Have you checked the Performance tab for any anomalies?
    – Aleksey Solovey
    Nov 19 '18 at 14:24










  • @AlekseySolovey - we use "Lato" font, opening performance tab on IE11 (or any of dev tools in that matter) is utterly slow and takes minutes to even open. We can check it next time we encounter this bug, but it also happens on other tabse as well. Is it possible that broken font can crash the rendering engine in the whole browser?
    – Lemurr
    Nov 19 '18 at 14:38






  • 1




    can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. Besides, I suggest you could try to use different computer or IE 11 version (you could try to upgrade the IE 11 to the latest version) to test your code to verify whether still meet this behavior.
    – Zhi Lv - MSFT
    Nov 20 '18 at 7:35




















  • no error in console ?
    – federico scamuzzi
    Nov 19 '18 at 14:14










  • @federicoscamuzzi - nothing
    – Lemurr
    Nov 19 '18 at 14:15










  • Your fonts broke. Do you use custom fonts? Have you checked the Performance tab for any anomalies?
    – Aleksey Solovey
    Nov 19 '18 at 14:24










  • @AlekseySolovey - we use "Lato" font, opening performance tab on IE11 (or any of dev tools in that matter) is utterly slow and takes minutes to even open. We can check it next time we encounter this bug, but it also happens on other tabse as well. Is it possible that broken font can crash the rendering engine in the whole browser?
    – Lemurr
    Nov 19 '18 at 14:38






  • 1




    can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. Besides, I suggest you could try to use different computer or IE 11 version (you could try to upgrade the IE 11 to the latest version) to test your code to verify whether still meet this behavior.
    – Zhi Lv - MSFT
    Nov 20 '18 at 7:35


















no error in console ?
– federico scamuzzi
Nov 19 '18 at 14:14




no error in console ?
– federico scamuzzi
Nov 19 '18 at 14:14












@federicoscamuzzi - nothing
– Lemurr
Nov 19 '18 at 14:15




@federicoscamuzzi - nothing
– Lemurr
Nov 19 '18 at 14:15












Your fonts broke. Do you use custom fonts? Have you checked the Performance tab for any anomalies?
– Aleksey Solovey
Nov 19 '18 at 14:24




Your fonts broke. Do you use custom fonts? Have you checked the Performance tab for any anomalies?
– Aleksey Solovey
Nov 19 '18 at 14:24












@AlekseySolovey - we use "Lato" font, opening performance tab on IE11 (or any of dev tools in that matter) is utterly slow and takes minutes to even open. We can check it next time we encounter this bug, but it also happens on other tabse as well. Is it possible that broken font can crash the rendering engine in the whole browser?
– Lemurr
Nov 19 '18 at 14:38




@AlekseySolovey - we use "Lato" font, opening performance tab on IE11 (or any of dev tools in that matter) is utterly slow and takes minutes to even open. We can check it next time we encounter this bug, but it also happens on other tabse as well. Is it possible that broken font can crash the rendering engine in the whole browser?
– Lemurr
Nov 19 '18 at 14:38




1




1




can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. Besides, I suggest you could try to use different computer or IE 11 version (you could try to upgrade the IE 11 to the latest version) to test your code to verify whether still meet this behavior.
– Zhi Lv - MSFT
Nov 20 '18 at 7:35






can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. Besides, I suggest you could try to use different computer or IE 11 version (you could try to upgrade the IE 11 to the latest version) to test your code to verify whether still meet this behavior.
– Zhi Lv - MSFT
Nov 20 '18 at 7:35














1 Answer
1






active

oldest

votes


















1














I suspect that this issue might be around the browser memory leak (considering that other tabs are also getting affected).



We had issues around memory leaks only in IE browser with Angular 1.3 (not the exact issue).



While this link might help you with further investigation, I'll mention how I used IE's memory profiling tool to help myself.
This memory profiling tool can be found in IE 11 dev tab.




  1. Click Start Profiling.

  2. Take a heap snapshot of your web app without performing any operation on your app.

  3. Perform some operation and take a heap snapshot again.

  4. Go back to the home page and see if some of the memory you allocated is getting freed or not.


Each heap snapshot also provides a deeper look into the objects allocated and how much memory each object is consuming.



I am attaching a snapshot for reference.



enter image description here






share|improve this answer





















  • did this answer help you?
    – ScrapCode
    Nov 30 '18 at 6:42










  • The problem is that IE freezes for over 10 minutes while opening the dev tools, and after couple of minutes of profiling it freezes again and crashes - and the issue happens after few hours. I believe it's because we already have hundreds (if not thousands) of JS files attached, and it cannot handle it. We'll try to profile it in Chrome though, but the memory leak is not that significant, though we will certainly look into this - thank you for the tip :)
    – Lemurr
    Dec 1 '18 at 9:04













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376479%2fweird-rendering-behavior-on-ie11-angular-1-5-11%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














I suspect that this issue might be around the browser memory leak (considering that other tabs are also getting affected).



We had issues around memory leaks only in IE browser with Angular 1.3 (not the exact issue).



While this link might help you with further investigation, I'll mention how I used IE's memory profiling tool to help myself.
This memory profiling tool can be found in IE 11 dev tab.




  1. Click Start Profiling.

  2. Take a heap snapshot of your web app without performing any operation on your app.

  3. Perform some operation and take a heap snapshot again.

  4. Go back to the home page and see if some of the memory you allocated is getting freed or not.


Each heap snapshot also provides a deeper look into the objects allocated and how much memory each object is consuming.



I am attaching a snapshot for reference.



enter image description here






share|improve this answer





















  • did this answer help you?
    – ScrapCode
    Nov 30 '18 at 6:42










  • The problem is that IE freezes for over 10 minutes while opening the dev tools, and after couple of minutes of profiling it freezes again and crashes - and the issue happens after few hours. I believe it's because we already have hundreds (if not thousands) of JS files attached, and it cannot handle it. We'll try to profile it in Chrome though, but the memory leak is not that significant, though we will certainly look into this - thank you for the tip :)
    – Lemurr
    Dec 1 '18 at 9:04


















1














I suspect that this issue might be around the browser memory leak (considering that other tabs are also getting affected).



We had issues around memory leaks only in IE browser with Angular 1.3 (not the exact issue).



While this link might help you with further investigation, I'll mention how I used IE's memory profiling tool to help myself.
This memory profiling tool can be found in IE 11 dev tab.




  1. Click Start Profiling.

  2. Take a heap snapshot of your web app without performing any operation on your app.

  3. Perform some operation and take a heap snapshot again.

  4. Go back to the home page and see if some of the memory you allocated is getting freed or not.


Each heap snapshot also provides a deeper look into the objects allocated and how much memory each object is consuming.



I am attaching a snapshot for reference.



enter image description here






share|improve this answer





















  • did this answer help you?
    – ScrapCode
    Nov 30 '18 at 6:42










  • The problem is that IE freezes for over 10 minutes while opening the dev tools, and after couple of minutes of profiling it freezes again and crashes - and the issue happens after few hours. I believe it's because we already have hundreds (if not thousands) of JS files attached, and it cannot handle it. We'll try to profile it in Chrome though, but the memory leak is not that significant, though we will certainly look into this - thank you for the tip :)
    – Lemurr
    Dec 1 '18 at 9:04
















1












1








1






I suspect that this issue might be around the browser memory leak (considering that other tabs are also getting affected).



We had issues around memory leaks only in IE browser with Angular 1.3 (not the exact issue).



While this link might help you with further investigation, I'll mention how I used IE's memory profiling tool to help myself.
This memory profiling tool can be found in IE 11 dev tab.




  1. Click Start Profiling.

  2. Take a heap snapshot of your web app without performing any operation on your app.

  3. Perform some operation and take a heap snapshot again.

  4. Go back to the home page and see if some of the memory you allocated is getting freed or not.


Each heap snapshot also provides a deeper look into the objects allocated and how much memory each object is consuming.



I am attaching a snapshot for reference.



enter image description here






share|improve this answer












I suspect that this issue might be around the browser memory leak (considering that other tabs are also getting affected).



We had issues around memory leaks only in IE browser with Angular 1.3 (not the exact issue).



While this link might help you with further investigation, I'll mention how I used IE's memory profiling tool to help myself.
This memory profiling tool can be found in IE 11 dev tab.




  1. Click Start Profiling.

  2. Take a heap snapshot of your web app without performing any operation on your app.

  3. Perform some operation and take a heap snapshot again.

  4. Go back to the home page and see if some of the memory you allocated is getting freed or not.


Each heap snapshot also provides a deeper look into the objects allocated and how much memory each object is consuming.



I am attaching a snapshot for reference.



enter image description here







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 29 '18 at 6:58









ScrapCode

96231226




96231226












  • did this answer help you?
    – ScrapCode
    Nov 30 '18 at 6:42










  • The problem is that IE freezes for over 10 minutes while opening the dev tools, and after couple of minutes of profiling it freezes again and crashes - and the issue happens after few hours. I believe it's because we already have hundreds (if not thousands) of JS files attached, and it cannot handle it. We'll try to profile it in Chrome though, but the memory leak is not that significant, though we will certainly look into this - thank you for the tip :)
    – Lemurr
    Dec 1 '18 at 9:04




















  • did this answer help you?
    – ScrapCode
    Nov 30 '18 at 6:42










  • The problem is that IE freezes for over 10 minutes while opening the dev tools, and after couple of minutes of profiling it freezes again and crashes - and the issue happens after few hours. I believe it's because we already have hundreds (if not thousands) of JS files attached, and it cannot handle it. We'll try to profile it in Chrome though, but the memory leak is not that significant, though we will certainly look into this - thank you for the tip :)
    – Lemurr
    Dec 1 '18 at 9:04


















did this answer help you?
– ScrapCode
Nov 30 '18 at 6:42




did this answer help you?
– ScrapCode
Nov 30 '18 at 6:42












The problem is that IE freezes for over 10 minutes while opening the dev tools, and after couple of minutes of profiling it freezes again and crashes - and the issue happens after few hours. I believe it's because we already have hundreds (if not thousands) of JS files attached, and it cannot handle it. We'll try to profile it in Chrome though, but the memory leak is not that significant, though we will certainly look into this - thank you for the tip :)
– Lemurr
Dec 1 '18 at 9:04






The problem is that IE freezes for over 10 minutes while opening the dev tools, and after couple of minutes of profiling it freezes again and crashes - and the issue happens after few hours. I believe it's because we already have hundreds (if not thousands) of JS files attached, and it cannot handle it. We'll try to profile it in Chrome though, but the memory leak is not that significant, though we will certainly look into this - thank you for the tip :)
– Lemurr
Dec 1 '18 at 9:04




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376479%2fweird-rendering-behavior-on-ie11-angular-1-5-11%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

MongoDB - Not Authorized To Execute Command

How to fix TextFormField cause rebuild widget in Flutter

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith