I took some effort to look into the issue in this post.
Javascript is Garbage collected language, so if the variables are correctly used, the memory usage should not increase in long term.
4 types of javascript memory leakage
1: Accidental global variables
2: Forgotten timers or callbacks
3: Out of DOM references
4: Closures
Chrome timeline of Memory didn't show any evidence of memory leakage.
Not all mobile browsers are slow on this blogger page. chrome, firefox, opera runs fast and smooth.
The mobile browser such as opera mini freeze when scrolling up/down the post, sometimes crash if I keep pressing the "Time Left" button.
Those lightweight mobile browser also runs poorly on blogger post without javascript, runs poorly on other people's blogger post, sometimes freeze during scrolling, especially difficult on rendering the blogger's header, footer and any portion with rich style.
Conclusion, the post in exam don't have memory leakage, the slowness is related to css rendering and blogger's header and footer in general.
At the client side, the solution is to avoid visiting blogger with lightweight mobile browser or open too many pages simultaneously.
On the server side, the action item is to modify blogger template, use lighter footer, header etc. to support wider spectrum of mobile browsers. The post should also avoid using css features whenever possible (for example, wrap code block inside <pre>code</pre> in HTML instead of copy/paste the code directly into Compose, which generate too much css style ).
