NaCl module crashed

[nie...@uah.edu]

Sorry for not providing any specific code; I'm away from my computer - just an open question:

 

After uploading a stripped-down working test application (just displays a GLES texture and accepts some input events - no audio) to the Chrome Web Store, I received...

 

"NaCl module crashed             index.html:1"

 

On most attempts nothing appears in the Chrome window, while on some attempts an error appears in the viewport after some time (the frowning puzzle piece).

 

Are there familiar issues associated with this error? I'm thinking maybe the page isn't ready when the application tries to start running, but I'm not really sure what's going on, and there doesn't seem to be much to go on. The Ctrl+Shift+J reports seem pretty-much okay.

 

Thank you very much.

 

Sincerely,

DanN

 

[Nick Bray]

"crashed" means that the process containing the nexe has disappeared.  Your nexe has probably segfaulted or called exit().  If there is a race between the nexe and the web page, it is an issue specific to your application.  You can use the PPB_Console interface to try and narrow down when the crash or exit occurs.  Or use GDB ( https://developers.google.com/native-client/dev/devguide/devcycle/debugging )  Note that you can cause early, non-obvious crashes during startup by returning corrupt function tables from PPP_GetInterface.

Alternatively, there may be a problem with your Chrome installation. Can you run any of the SDK examples?

 

--
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-di...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[nie...@uah.edu]

Thank you, Nick, for those valuable tips. Chrome should be good, but I'll try packing one of the examples and to see if I can get that far.
Sincerely,

DanN

On Tuesday, July 16, 2013 10:36:11 AM UTC-5, Nick Bray wrote:

"crashed" means that the process containing the nexe has disappeared.  Your nexe has probably segfaulted or called exit().  If there is a race between the nexe and the web page, it is an issue specific to your application.  You can use the PPB_Console interface to try and narrow down when the crash or exit occurs.  Or use GDB ( https://developers.google.com/native-client/dev/devguide/devcycle/debugging )  Note that you can cause early, non-obvious crashes during startup by returning corrupt function tables from PPP_GetInterface.

Alternatively, there may be a problem with your Chrome installation. Can you run any of the SDK examples?

On Tue, Jul 16, 2013 at 8:01 AM, <nie...@uah.edu> wrote:

Sorry for not providing any specific code; I'm away from my computer - just an open question:

 

After uploading a stripped-down working test application (just displays a GLES texture and accepts some input events - no audio) to the Chrome Web Store, I received...

 

"NaCl module crashed             index.html:1"

 

On most attempts nothing appears in the Chrome window, while on some attempts an error appears in the viewport after some time (the frowning puzzle piece).

 

Are there familiar issues associated with this error? I'm thinking maybe the page isn't ready when the application tries to start running, but I'm not really sure what's going on, and there doesn't seem to be much to go on. The Ctrl+Shift+J reports seem pretty-much okay.

 

Thank you very much.

 

Sincerely,

DanN

 

--
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.

[nie...@uah.edu]

I got my test app working last night, but apparently I was blocked from the Store or something due to uploading too many times (for testing only). I am still able to connect on another machine (or from Internet Explorer on this machine, but of course it doesn't support installing apps from Chrome Store).

Does anyone know what I can do to get off the blocklist?

Thanks very much.

Sincerely,

DanN

[nie...@uah.edu]

 I was too hasty: I should have said that the Chrome Web Store is "unavailable" - likely I was not blocked. (The search engine said "You've visited this page many times", which somehow I misread last night as "You've visited this page TOO many times") Why it is not working for me now is still a mystery, though.

Any help is still very appreciated.

DanN

[nie...@uah.edu]

Okay, works now - sorry all the messages (just had to close all instances of Chrome in task manager)

[禁差]

2013/7/16 <nie...@uah.edu>

 

--

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-di...@googlegroups.com.

[Madan Lp]

Hi,

I am facing the same issue while mounting the network shared location and reading file from there up to 300 MB its taking longer time and after some times its throws "NativeClient: NaCl module crashed      index.html:1"

Using Chrome App Network File Share application to mount the shared location on my Chromebook machine.

Please share how I can resolve this issue.

Regards

Madan

[Sam Clegg]

On Fri, Oct 14, 2016 at 6:37 AM, Madan Lp <madan...@gmail.com> wrote:
> Hi,
>
> I am facing the same issue while mounting the network shared location and
> reading file from there up to 300 MB its taking longer time and after some
> times its throws "NativeClient: NaCl module crashed index.html:1"
>
> Using Chrome App Network File Share application to mount the shared location
> on my Chromebook machine.

Probably best to file a bug against the app itself:
https://github.com/GoogleChrome/chromeos_network_file_share.

>
> Please share how I can resolve this issue.
>
>
> Regards
> Madan
>
>
>
> On Tuesday, July 16, 2013 at 8:31:58 PM UTC+5:30, Daniel Nielsen wrote:
>>
>> Sorry for not providing any specific code; I'm away from my computer -
>> just an open question:
>>
>> After uploading a stripped-down working test application (just displays a
>> GLES texture and accepts some input events - no audio) to the Chrome Web
>> Store, I received...
>>
>> "NaCl module crashed index.html:1"
>>
>> On most attempts nothing appears in the Chrome window, while on some
>> attempts an error appears in the viewport after some time (the frowning
>> puzzle piece).
>>
>> Are there familiar issues associated with this error? I'm thinking maybe
>> the page isn't ready when the application tries to start running, but I'm
>> not really sure what's going on, and there doesn't seem to be much to go on.
>> The Ctrl+Shift+J reports seem pretty-much okay.
>>
>> Thank you very much.
>>
>> Sincerely,
>> DanN
>>
>

> --
> 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-di...@googlegroups.com.
> To post to this group, send email to native-cli...@googlegroups.com.

> Visit this group at https://groups.google.com/group/native-client-discuss.
> For more options, visit https://groups.google.com/d/optout.