- September 6, 2014 at 7:56 pm #31805
On various PC configurations we are seeing an access violation when calling eglInitialize(). Typically on GeForce and AMD based PCs our test applications work just fine, but on others the application experiences an “Access violation executing location 0x00000000.”. The app is a simple framework, starting with an eglGetDisplay() followed by eglInitialize(), etc.
We’re using the latest PowerVR SDK 3.3 R2. One of the offending configurations is a clean installation of:
Windows 8.1 Pro x64
Intel Pentium Dual CPU T2390
Intel 965 Express Chipset Family
385MB available graphics memory
Is the crash due to the configuration not being supported, or is this a bug in Power SDK? Is there a list of HW configurations that are supported? If this is not a bug, is there a function we can call before calling eglInitialize() in order to identify if the system is supported?September 6, 2014 at 7:59 pm #38966
btw, here’s the call stack:
[Frames below may be incorrect and/or missing]
Test.exe!InitializeEGL(HDC__ * hdc)September 8, 2014 at 8:47 am #38967
Just to clarify – are you reporting an issue with our PVRVFrame OpenGL ES emulation? If so, can you share your application source or binary with us? This will enable us to reproduce the issue locally.
Do the graphics drivers meet PVRVFrame’s requirements? (listed in the PVRVFrame page of our site)
If you would prefer to send the files to us confidentially instead of posting links to them on the forum, you can attach them to a support ticket here.