[4.7.2] "profilegpu" does not work on Android ES31+AEP

Development Platform & Builds Debugging, Optimization, & Profiling
, , , ,
1

the “profilegpu” command causes the follow error on Android ES31+AEP :

Fatal error: [File:G:\uesrc\UnrealEngine\Engine\Source\Runtime\OpenGLDrv\Private\OpenGLDevice.cpp] [Line: 305] D/UE4 ( 8126): [API][Error][High][1282] GL_INVALID_OPERATION error generated. Cannot begin query on an active query object.

reproable with any map.
Tested on Shield Tablet with OTA2.2

2

Howdy bethor,

Thank you for reporting this issue. I have just attempted a quick repro of this issue internally and have been unsuccessful so far. Here are the steps that i took:

  1. Deployed a template project to a Shield Tablet on 2.2.1
  2. Once deployed, I opened the console command in the level and entered ‘profilegpu’
  3. I was unable to see any errors on the device.

Would there be any steps that I would be missing? Any additional information would be greatly appreciated.

Thanks and have a great day!

3

Hello Sean,

That is strange. Just in case I tried making a clean sync and build on a different pc, and see the issue there too.

Some possible areas of mismatch I can think of:

  • Are you building from the release branch (not master)?

  • Are you using a Development build?

  • Are you entering the “profilegpu” command directly on the device, after bringing the console up with a 4 finger tap?

  • Are you checking for errors in logcat (there is no dialog box)

  • Does your shield tablet version details match the following:

34227-settings_20150315_132115.jpg
34227-settings_20150315_132115.jpg1920×1200 97 KB

I’ve also put a test apk built on my machine here:

https://www.dropbox.com/s/ty0i0ixxdihj7e6/profilegpurepro0315.zip?dl=0

If you can try this, it should tell us if the mismatch is on the build itself or the device’s behavior.

Thanks for looking into this.

4

Sean,
I cannot reproduce the issue on the master branch, so I suppose I just need to wait for the 4.8 release.
Feel free to close this issue, thanks!

5

Howdy bethor,

Glad to hear that this issue has been resolved for you in the Master branch of UE4. If you run across this issue in a future build, be sure to reopen this issue so that I may be able to further investigate.

Also, just a reminder that the Master branch is not a stable build of UE4. Be cautious when developing a project in that build. I would recommend opening a copy of your project so that you will have a back up if anything does go wrong.

Thanks and have a great day!

6

I faced the similar problem, but I received no crash log.
I was using the UE4.19.