- From: Rick Mann <rmann@latencyzero.com>
- Date: Wed, 8 Mar 2017 15:14:26 -0800
- To: luke@mozilla.com
- Cc: M Ghazanfar Saeed <MGhazanfar.Saeed@imgtec.com>, John Henry <john@iamjohnhenry.com>, David Ross <sw1ayfe@gmail.com>, "public-webassembly@w3.org" <public-webassembly@w3.org>
Should the group set up a Discourse server somewhere to handle discussions? Or monitor Stackoverflow? > On Mar 8, 2017, at 07:09 , Luke Wagner <lwagner@mozilla.com> wrote: > > Probably this isn't the right mailing list to discuss demos and issues. As we get more and beefier demos up on github.com/webassembly/website, issues on that repo would be a good venue for general problems, and otherwise issues filed with individual browsers (as described in http://webassembly.org/community/feedback), would be appreciated. > > (That particular issue you mention is known and caused by the demo doing a lot of work during initialization without returning to the event loop. There's still ongoing work to improve the demo including doing less work during initialization.) > > Cheers, > Luke > > > On Wed, Mar 8, 2017 at 4:59 AM, M Ghazanfar Saeed <MGhazanfar.Saeed@imgtec.com> wrote: > FWIW, ‘webassemblydemo’ failed on latest Firefox 52 (snapshot attached) on my Toshiba PORTEGE Z930-14C laptop (compiling web assembly step apparently seems to be successful). I am able to run ‘Tanks’ demo though. > > > > Regards, > > Saeed > > > > From: John Henry [mailto:john@iamjohnhenry.com] > Sent: 07 March 2017 21:17 > To: David Ross; public-webassembly@w3.org > Subject: Re: Can not find any browser that works ... > > > > Hey Doug, > > > > Web assembly just went live in Firefox 52 today. You should be able to download the latest version today and run that demo. > > Here's another interesting demo: https://mzl.la/webassemblydemo > > > > Best, > > -- John > > > > On Mon, Mar 6, 2017 at 2:26 AM David Ross <sw1ayfe@gmail.com> wrote: > > WASM is being switched on from Firefox 52 (7 March, 2017). Chrome will follow the next version rollout, the next week possibly? > > > > I'm using Nightly (54) on Arch Linux on a 2008 model Dell laptop running 16Gb RAM and > > > > 1) now works fine. It did not a few months back when I last tested. > > 2) not sure of your precise test here to compare > > > > > > On Thu, 2017-03-02 at 09:25 -0700, Doug Royer wrote: > > Just started playing with wasm. > > Tried several version of Firefox and Chrome. > > Running Linux, Fedora-24 > > (1) http://webassembly.org/demo/ > > Starts up a loading page, then after the load slider is > finished, products a BLANK page > > (2) The HelloWorld demo, generates: > > An Exception thrown, see JavaScript console, on the browsers. > > (2.1) the "emrun --no_browser --port 8080 ." > prints this when the browser access the page: > > The html page you are running is not emrun-capable. Stdout, > stderr and exit(returncode) capture will not work. Recompile > the application with the --emrun linker flag to enable this, or > pass --no_emrun_detect to emrun to hide this check. > > (2.2) Compiling with "--emrun", produces the same error as (2) > > (2.3) Compiling with "--no_emrun_detect", results in (at compile time) > > clang-3.9: error: unsupported option '--no_emrun_detect' > ERROR:root:compiler frontend failed to generate LLVM bitcode, > halting > > Questions: > > What browsers versions work? > > Are the http://webassembly.org/getting-started/developers-guide/ > incorrect? > > Thanks! > > -- Rick Mann rmann@latencyzero.com
Received on Wednesday, 8 March 2017 23:15:35 UTC