pNACL(Native client) load fail
Reported by
sridhar....@gmail.com,
Mar 18 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36 Steps to reproduce the problem: 1. Try to open any app which uses native client , example: https://gonativeclient.appspot.com/demo/bullet What is the expected behavior? App load should be success and works as per expectation What went wrong? Loading NACL module fails with the following error: 45468:1 NativeClient: Insufficient memory to allocate untrusted address space 45468:1 NativeClient: geAlloc: VirtualAlloc(*,0x40000000) failed 345468:1 NativeClient: [2636,5576:05:23:09.195000] NaClPageAlloc: VirtualAlloc(*,0x40000000) failed 45468:1 NativeClient: [2636,5576:05:23:09.195000] NaClPageAllocRandomized: failed (12), dropping hints 45468:1 NativeClient: [2636,5576:05:23:09.195000] NaClPageAlloc: VirtualAlloc(*,0x40000000) failed 45468:1 NativeClient: [2636,5576:05:23:09.209000] NaCl LoadApp failed. Transferring logs before exit. Did this work before? N/A Chrome version: 57.0.2987.98 Channel: stable OS Version: Windows 7 32 bit Did this work before? N/A Chrome version: 57.0.2987.98 Channel: stable OS Version: 7 Flash Version: Chrome version: 57.0.2987.98 OS Version: Windows 7 32 bit
,
Mar 21 2017
Tested this issue on Windows-10 using chrome latest stable #57.0.2987.110. By opening the above link observed the page loads as expected and able to move and add different objects. sridhar@ Could you please confirm what's the actual issue you are facing? Please upgrade your chrome to latest stable #57.0.2987.110 and recheck this issue. If issue still persists please reply to this comment with actual behavior. Thanks!
,
Mar 23 2017
,
Mar 23 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by ligim...@chromium.org
, Mar 20 2017