> Todd wrote: > I assume that it is a memory leaking error. Has anyone had this problem of > calling LiveCode function from a JavaScript function in the browser?? This > is a HUGE problem for us as the app cannot be shipped. Libbrowser eats on desktop up to 5 MByte of memory per second. Bug #20012.