<div dir="ltr"><div>Hi Adam,</div><div><br></div><div>I do agree that they are not in any way deadly. Now I see that I have chosen the wrong words when saying "substantial memory leak" and "crucial". Probably, I have got too excited when I found the reason and a possible fix for the leak. Sorry about the bad choice of words.</div><div><br></div><div>Sincerely,</div><div>Saulo</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Aug 28, 2016 at 9:46 PM, Adam Chlipala <span dir="ltr"><<a href="mailto:adamc@csail.mit.edu" target="_blank">adamc@csail.mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Oh, I definitely understand the
motivation for hunting down this kind of problem, and I appreciate
your efforts. I run a number of single-page Ur/Web apps in
production. The fact that no one is complaining about them
provides some evidence that this isn't a deadly problem in
practice.<span class=""><br>
<br>
On 08/28/2016 08:18 PM, Saulo Araujo wrote:<br>
</span></div><span class="">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>Hi Adam,</div>
<div><br>
</div>
<div>Memory leaks in the JavaScript runtime like these are not
important in classical web applications because the browser
moves to a new page very frequently, thus freeing all memory
that the previous page has allocated. However, In
single-page applications (<a href="https://en.wikipedia.org/wiki/Single-page_application" target="_blank">https://en.wikipedia.org/<wbr>wiki/Single-page_application</a>),
the browser loads just one page, which makes the absence of
memory leaks in the JavaScript runtime crucial. Maybe most
of the applications that are in production are of the
classical kind. This would explain why there are no
complaints about memory leaks in the JavaScript runtime. As
I am developing a single-page application (<a href="https://github.com/saulo2/timesheet-ur" target="_blank">https://github.com/saulo2/<wbr>timesheet-ur</a>),
this is an important matter to me. Therefore, I am willing
to contribute by hunting those leaks and suggesting fixes.
Also, I believe that more and more single-page applications
will be developed with Ur/Web rather than classical ones.</div>
</div>
<div><br>
</div>
<div>Sincerely,</div>
<div>Saulo</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Aug 26, 2016 at 1:12 PM, Adam
Chlipala <span dir="ltr"><<a href="mailto:adamc@csail.mit.edu" target="_blank">adamc@csail.mit.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 08/24/2016 03:02 PM, Saulo Araujo wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am happy to say that your patch also fixes the memory
leak.<br>
</blockquote>
<br>
</span>
OK, great.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I believe there is another memory leak in the JavaScript
runtime (see the end of the previous message). I am
gonna look into it.<br>
</blockquote>
<br>
</span>
I'll appreciate any help finding more memory leaks, though
in the foreseeable future I probably won't be spending time
tracking them down. There don't seem to have been any
complaints yet about memory leaks in connection to
production applications.</blockquote>
</div>
</div>
</blockquote>
</span></div>
<br>______________________________<wbr>_________________<br>
Ur mailing list<br>
<a href="mailto:Ur@impredicative.com">Ur@impredicative.com</a><br>
<a href="http://www.impredicative.com/cgi-bin/mailman/listinfo/ur" rel="noreferrer" target="_blank">http://www.impredicative.com/<wbr>cgi-bin/mailman/listinfo/ur</a><br>
<br></blockquote></div><br></div>