Possible duplicate of https://github.com/golang/go/issues/35111 (garbage collection of js.Value references) which was recently fixed.
Please try with gotip (https://godoc.org/golang.org/dl/gotip) or build from source. Note that the fix for #35111 made js.Value equality tests a compile time error, so you might need to update your code to use the new IsNull, IsUndefined, Equal, IsNaN. -- elias On Sunday, November 10, 2019 at 11:12:14 AM UTC+1, mihai barbulescu wrote: > > I'm trying to build a web/client app using Go (compiled to wasm). The > issue is that the browser(both FF and Chrome) gets stuck(i.e and I get a > notice "A page is slowing your browser | Stop it | Wait" ) shortly after > some minimal interaction (initial page is loaded and a form is processed). > I took a Memory sample using firefox developer tools(see the print-screen) > but I can't find what exactly the culprit. Any idea what could cause it or > how to better debug it? Most of the memory seems to go into > runtime.ScheduleTimeoutEvent. > The program is built using Go tip. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/7d7f869b-6700-48c2-be57-659b73432d63%40googlegroups.com.
