NaCl Development Environment - crash on startup

[Michael Fox]

Not sure if this is the right place to report, but:

I tried installing NaCl Development Environment under Chrome 56.0.2924.87 (64-bit) and it crashes about 1 second after startup. I barely have time to see the box which says something like "Performing Initial devenv Setup" and then its dead.

I tried two different (mac) computers and got the same result.

Lots of people are making similar complaints for several months on the products support page, without answer:

https://chrome.google.com/webstore/detail/nacl-development-environm/aljpgkjeipgnmdpikaajmnepbcfkglfa/support

I've never used this before so I don't know how to investigate further.

[Michael Fox]

Works if I download an older version of Chrome, specifically: 54.0.2840.71 (Official Build) (64-bit)

I also notice this thread is probably talking about the same issue: https://groups.google.com/forum/#!topic/native-client-discuss/XFJCgs8kY7w

[Bennet Yee (余仕斌)]

have you tried going to chrome://flags and turning on NaCl (to enable it to run everywhere, as opposed to only from the chrome web store)?  i seem to recall having to do this to get the NaCl dev env installed.  not sure if the flag is needed after installation.  -bsy

--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsub...@googlegroups.com.
To post to this group, send email to native-client-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.

--

bennet s yee
i usually don't capitalize due to mild tendonitis

[Michael Fox]

Yes I did. That's necessary in Chrome 54 but does not help the crashing in Chrome 56.

On Mar 3, 2017 9:36 AM, "Bennet Yee (余仕斌)" <benne...@gmail.com> wrote:

have you tried going to chrome://flags and turning on NaCl (to enable it to run everywhere, as opposed to only from the chrome web store)?  i seem to recall having to do this to get the NaCl dev env installed.  not sure if the flag is needed after installation.  -bsy

On Fri, Mar 3, 2017 at 9:30 AM, Michael Fox <415...@gmail.com> wrote:

Works if I download an older version of Chrome, specifically: 54.0.2840.71 (Official Build) (64-bit)

I also notice this thread is probably talking about the same issue: https://groups.google.com/forum/#!topic/native-client-discuss/XFJCgs8kY7w

On Friday, March 3, 2017 at 9:00:15 AM UTC-8, Michael Fox wrote:

Not sure if this is the right place to report, but:

I tried installing NaCl Development Environment under Chrome 56.0.2924.87 (64-bit) and it crashes about 1 second after startup. I barely have time to see the box which says something like "Performing Initial devenv Setup" and then its dead.

I tried two different (mac) computers and got the same result.

Lots of people are making similar complaints for several months on the products support page, without answer:

https://chrome.google.com/webstore/detail/nacl-development-environm/aljpgkjeipgnmdpikaajmnepbcfkglfa/support

I've never used this before so I don't know how to investigate further.

--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsubscri...@googlegroups.com.

To post to this group, send email to native-client-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.

--

bennet s yee
i usually don't capitalize due to mild tendonitis

--
You received this message because you are subscribed to a topic in the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/native-client-discuss/V-wgApiBjJA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to native-client-discuss+unsub...@googlegroups.com.

[Bennet Yee (余仕斌)]

ah. i guess i should have tried it out before the knee-jerk answer. my apologies. i see the same problem too.  i'm not sure if google is allocating any engineering to NaCl these days, but hopefully if there are you'll get a response on one of these groups (+native-client-dev).  if i had to guess, it's some pepper API change.

To unsubscribe from this group and all its topics, send an email to native-client-discuss+unsubscri...@googlegroups.com.

To post to this group, send email to native-client-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsub...@googlegroups.com.

To post to this group, send email to native-client-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.

[lael.c...@gmail.com]

It‘s definitely a regression which had been confirmed by developers. It affect several apps, I mean not only the development environment.

You can see it’s report.

If you still want to use the in‑browser extension just use old versions of chrome or chromium until the year for the bug fix come.

[lael.c...@gmail.com]

Here’s the bug report for reference