-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oculus VR trace fails to replay with 1.3.1 #2586
Comments
They should be in your %APPDATA%\Temp. Gapis.log and gapic.log.
…On Sat, Feb 2, 2019, 9:02 AM Rishi Ranjan ***@***.***> wrote:
Release 1.3.1 is the first release which enabled capturing logs for Oculus
Mobile VR. But replay keeps failing consistently. Where are debug logs
saved for GAPID?
com.oculus.vrcubeworldsv_20190202_0550.gfxtrace.zip
<https://github.com/google/gapid/files/2824465/com.oculus.vrcubeworldsv_20190202_0550.gfxtrace.zip>
[image: replay_fails]
<https://user-images.githubusercontent.com/5673695/52165035-0fa3bf80-26b0-11e9-87f2-45285abf8981.PNG>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2586>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIn9DOBpvp-cqFocccDRFAsiZpQmv5fAks5vJZqGgaJpZM4afmn3>
.
|
I see following assertion failing.
|
@AWoloszyn Do you have any suggestion on WA for this issue. |
That is correct. The first thing you can try is updating the version of SPIRV-Tools that we use. This would be a matter of updating
You may have to also update SPIRV-Headers as well to its updated version. |
Tried updating SPIRV-Tools and SPIRV-Headers but still getting compilation error.Will update other repos and see if I can get rid of these compilation error. |
Did following changes to make some progress. Still one compilation error is there which I need to fix.
|
@AWoloszyn I am able to compile gapid with latest SPIRV-Tools and generated header. But I am still getting same exception. I have attached all the files I had to change on master branch. Let me know if you have any other suggestions. Should I change other SPIRV repos ?
|
@AWoloszyn I changed all four SPIRV repos and tried but it also didn't help. Let me know if you have any other suggestions. |
KhronosGroup/SPIRV-Tools#2203 had similar issue. I did confirm that I have this fix. I don't understand SPIRV much so will continue looking and decide if I should open a bug on SPIRV-Tools. |
Sorry, I was out of the country last week. I am trying to figure out where spirv-opt is being invoked in our chain. If you are trying to replay on the original device (it does not appear like this is the case in your screenshot) tip of tree should work, as it avoids a lot of this SPIR-V work. #2600 Fixes one of the issues, in that now your sample replays, at least on my desktop. I do not think it is replaying correctly, but it gets further. |
@AWoloszyn I had been trying to replay in on original device but it crashes there also. I will try #2600 and let you know. |
@AWoloszyn I tried #2600 but it didn't help. I will do a clean bazel build and see if it helps. |
With a clean build also, I am getting same issue. |
@AWoloszyn Do you have any other suggestion? |
Hey, sorry for the slow reply. We were working on getting 1.4 out the door. |
@AWoloszyn I tried 1.4 but it has gone worse with Oculus VR. It crashes right away. Attaching logs. |
@AWoloszyn I can help with any logs to fix the issue. I need this working to deliver on a critical project so let me know if I can facilitate anything. |
Do you happen to have the |
Attaching full adb log and filtered one with GAPID. |
I think the link to your full adb log may be incorrect. |
Attaching zipped version of full adb log. |
Thanks, that was somewhat helpful. It looks like there is no crash, but the application in question is just shutting itself down (relatively gracefully)
GAPID functioning normally here
Surface View destroyed for some reason
|
Before dumping the adb logs, I had closed both gapid on PC and application on Android so I don't hit the logcat buffer wrap around. That's why you might be seeing the application closing gracefully. |
The time difference here was only 6ms though, which seems odd to me. |
With 1.3.1 I was able to capture the logs but was not able to open it. I tried opening logs that I captured with 1.3.1 in 1.4 but it doesn't work. |
Since you were able to trace on 1.3.1, can you try replaying on device rather than on desktop for 1.3.1? When replaying on device, SPIRV-Cross should not even be in the code path. There was a bug, which was fixed in b81b362, so if you could apply that patch (it's a one line change) on top of 1.3.1 and see if that works for you, it might get you going in the mean time. |
I see this issue with 1.3.1 with this fix also. Will try by going back to 1.3.1. if I see issue there also, I have moved to newer OVR SDK. Will go back to older one and try to isolate the issue. |
Tried all the older SDK also which had worked with 1.3.1 but now it's not working. Not sure if any Android upgrade since then is breaking the capture. |
Hi! I'm trying to reproduce the issue here. Can you confirm which device are you using? Also, which CubeWorld demo are you tracing? Is it VrCubeWorld_Vulkan? |
@pau-baiget I am using Galaxy S8. I am using VrCubeWorld_SurfaceView. We are building our own Cloud XR solution on top of this sample but I can make progress there once I am able to trace basic demo. |
Great, thanks! Can you please attach here the output of the following command in the root GAPID folder? $ ./gapit devices (I want to check whether I have the same Galaxy S8 here with same driver version). |
Are you looking for this? I am on Windows 10 so ran 'gapit devices' from comamnd line and attached the log. |
Hi @pau-baiget , were you able to reproduce this? |
I'm waiting to get a Gear VR device so I can enable the Gear VR Service on my Galaxy S8, necessary to run the VrCubeWorld_SurfaceView app. |
FYI.. You can launch the application without HMD if you enable Dev mode: https://developer.oculus.com/documentation/mobilesdk/latest/concepts/mobile-device-setup/ Don't remember if it let's you enter this dev mode without setting it up with HMD first time. |
I tried this after resettign my S8. You can start debugging VrCubeWorld_SurfaceView without Gear VR HMD also. You will need to add OSIG file to your project before the dev mode settings from Note: If you do not see the Developer Mode toggle switch after tapping VR Service Version several times, close the Gear VR Service and relaunch and you should see it. |
Sorry for late response. I got the Gear VR headset and was able to run the app using GAPID. I could obtain a trace and open it with GAPID 1.4 (I can also open the trace you attached in the ticket description, they look similar). The trace has 4 contexts:
I did find the reported error while trying to replay on desktop, but replaying on the device didn't cause any error or crash. I'm using OVR_sdk_mobile v. 1.21. and a Samsung Galaxy S9. I will try this afternoon with the 1.22 and my personal Galaxy S8 to check for any different behavior. |
@pau-baiget Thanks for the response. I am also able to replay the trace on phone now with 1.4. Not sure if resetting the phone helped. I tried replaying the trace on two different PCs but both of them failed. One has Nvidia 1060M and other has GTX 970 desktop GPU. I can start debugging my issue with phone so will I am unblocked now for my tracing and debugging. |
I am able to replay the log that I attached to this issue but I am not able to capture new trace using 1.4. |
Can you try with 1.5.0? |
It worked once for me with 1.5.0 but once I rebooted my Laptop it is stuck at same issue. I will upload the logs from 1.5.0 in sometime. |
Do you have a screenshot of your trace options? I am wondering if something in there that can help. |
Tried 1.5.0 on a freshly installed PC also and I see exactly the same issue. |
Release 1.3.1 is the first release which enabled capturing logs for Oculus Mobile VR. But replay keeps failing consistently. Where are debug logs saved for GAPID?
@AWoloszyn Please let me know if I can provide some logs to resolve this.
com.oculus.vrcubeworldsv_20190202_0550.gfxtrace.zip
The text was updated successfully, but these errors were encountered: