Oculus Quest Crash after I call "Print String" node

beogivaljr · December 15, 2020, 11:50pm

My game keeps on crashing exactly after I print something to the console. It doesn’t happen to the windows version and it also doesn’t happen when I pack the game in shipping mode.
I’m pretty sure it’s the print node because I’ve managed to isolate the issue.

I created a new blank project with the virtual reality template and the crash keeps on happening. I’m new here so I’m not sure what king of info I need to provide, but I’ll leave here my log from logcat.

[Update] I managed to isolate the setting that causes it. It only happens when I add: Platform > Android > Advanced APK Packaging > Package for Oculus Mobile devices [Quest/Quest2]. Obviously something I can’t leave empty.

12-13 19:00:57.639 22332 22350 D UE4     : [2020.12.13-21.00.57:639][ 39]LogBlueprintUserMessages: [BP_TemplateGameInstance_C_2147482600] LEVEL MANAGER VALID
12-13 19:00:57.639 22332 22350 D UE4     : [2020.12.13-21.00.57:639][ 39]LogBlueprintUserMessages: [BP_TemplateGameInstance_C_2147482600] _2_13_3_14_9_12_10_8_1_15_11_7_5_6_4_16
12-13 19:00:57.643 22332 22350 D UE4     : [2020.12.13-21.00.57:643][ 39]LogSlate: Took 0.002127 seconds to synchronously load lazily loaded font '../../../Engine/Content/Slate/Fonts/Roboto-Regular.ttf' (155K)
12-13 19:00:57.664 22332 22428 D UE4     : [2020.12.13-21.00.57:664][ 41]LogProfilingDebugging: Allocated a 1024 x 1024 texture for HMD canvas layer
12-13 19:00:57.706  1917 22404 I VrRuntimeService: CreateSwapChain: 3661933971
12-13 19:00:57.707  1917 22404 I VrRuntimeService: CreateSwapChain: api:gles 0 0x8c43 1024 1024 1 3 1 0 14
12-13 19:00:57.731  1917 22404 I VrRuntimeServer: CreateTextureSwapChain: result importswapchaingles 1
--------- beginning of crash
12-13 19:00:57.737 22332 22428 F libc    : Fatal signal 7 (SIGBUS), code 1, fault addr 0x7 in tid 22428 (RenderThread)
12-13 19:00:57.795  1917 22287 I TimeWarp: SetSchedFifo( tid=22350, pol=2, pri=0 ) succeeded
12-13 19:00:57.795  1917 22287 I TimeWarp: SetSchedFifo( tid=22387, pol=2, pri=0 ) succeeded
12-13 19:00:57.795  1917 22287 I TimeWarp: SetSchedFifo( tid=22430, pol=2, pri=0 ) succeeded
12-13 19:00:58.062   721 22270 I [CT]    : VIPER: Vega=false,Status=6DoF,TRACKING,KF=0,Inl=132,Pts=0,Jit=0.1mm,Issues(Cam/min=0.0,IMU/min=0.0),Exp=(6.0ms,g=6.0,I=69)(6.3ms,g=6.0,I=75)(6.0ms,g=6.0,I=81)(6.0ms,g=4.0,I=75)
12-13 19:00:58.406 22332 22400 I VrApi   : FPS=1/72,Prd=0ms,Tear=7,Early=0,Stale=57,VSnc=0,Lat=1,Fov=4,CPU4/GPU=4/4,2304/670MHz,OC=FF,TA=0/E0/E0,SP=N/N/N,Mem=1804MHz,Free=1126MB,PSM=0,PLS=0,Temp=34.0C/0.0C,TW=2.70ms,App=13.96ms,GD=0.62ms,CPU&GPU=0.00ms,LCnt=1,GPU%=0.98,CPU%=0.25(W0.29),DSF=1.00
12-13 19:00:58.409   618   618 W         : debuggerd: handling request: pid=22332 uid=10407 gid=10407 tid=22428
12-13 19:00:58.518 22431 22431 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-13 19:00:58.519 22431 22431 F DEBUG   : Build fingerprint: 'oculus/vr_monterey/monterey:7.1.1/NGI77B/1201830.9360.0:user/release-keys'
12-13 19:00:58.519 22431 22431 F DEBUG   : Revision: '0'
12-13 19:00:58.519 22431 22431 F DEBUG   : ABI: 'arm64'
12-13 19:00:58.520 22431 22431 F DEBUG   : pid: 22332, tid: 22428, name: RenderThread  >>> com.MyComp.MyGame <<<
12-13 19:00:58.520 22431 22431 F DEBUG   : signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0x7
12-13 19:00:58.520 22431 22431 F DEBUG   :     x0   0000007f7577b988  x1   ffffffffffffffff  x2   0000000000000001  x3   0000000000000001
12-13 19:00:58.520 22431 22431 F DEBUG   :     x4   0000000000000002  x5   0000007f79ee9460  x6   0000000000000001  x7   0000000000000000
12-13 19:00:58.520 22431 22431 F DEBUG   :     x8   0000000000000007  x9   659bc531269ea62b  x10  0000007f5994feb8  x11  0000007f5994ff20
12-13 19:00:58.520 22431 22431 F DEBUG   :     x12  0000007f8c5b97f8  x13  0000000000000008  x14  0000000000000040  x15  0000007f79ee99d0
12-13 19:00:58.520 22431 22431 F DEBUG   :     x16  0000007f8cd54ba8  x17  0000007fab6e192c  x18  000000000000ffff  x19  0000007f7577b988
12-13 19:00:58.520 22431 22431 F DEBUG   :     x20  0000000000000000  x21  0000007f8ce95780  x22  0000007f7571e0e0  x23  0000500000000000
12-13 19:00:58.520 22431 22431 F DEBUG   :     x24  0000007f8ce95792  x25  0000007f8cee16c8  x26  0000007f79ee9460  x27  0000007f79eea4e8
12-13 19:00:58.520 22431 22431 F DEBUG   :     x28  0000000000000000  x29  0000007f79ee9400  x30  0000007f8ad7b3b8
12-13 19:00:58.520 22431 22431 F DEBUG   :     sp   0000007f79ee93b0  pc   0000007f868d3554  pstate 0000000060000000
12-13 19:00:58.521 22431 22431 F DEBUG   : 
12-13 19:00:58.521 22431 22431 F DEBUG   : backtrace:
12-13 19:00:58.522 22431 22431 F DEBUG   :     #00 pc 00000000009ea554  /data/app/com.MyComp.MyGame-1/base.apk (offset 0x283e9000)
12-13 19:00:58.522 22431 22431 F DEBUG   :     #01 pc 0000000004e923b4  /data/app/com.MyComp.MyGame-1/base.apk (offset 0x283e9000)
12-13 19:00:58.527   721 22270 I [CT]    : VIPER:MAP_MANAGER: State: TRACKING_PERSISTENT, UUID=2ef056bb-ff62-4dd6-aab6-94151e0567fe, Num. Persistent maps = 3,  Persistent maps:2ef056bb-ff62-4dd6-aab6-94151e0567fe,8aea0f21-215d-4323-8d48-b89d5aa434c8,2ef955fe-9a08-45f5-ab6a-13c4891e038f,, Ser. Disabled = 00000000-0000-0000-0000-000000000000

xadamxful · December 20, 2020, 12:05am

I can confirm I’m getting the same behavior in 4.26 with Oculus Quest 1, have you submitted a bug report?

beogivaljr · December 20, 2020, 12:51am

Yep I did But I left the question here in case I did something wrong and no one else is getting the same error. Thanks for confirming.

xadamxful · December 20, 2020, 1:15am

Great, thank you. I’ll upvote it when they add it to the list.

xadamxful · January 3, 2021, 5:08pm

I started going through deleting all my print strings before I realised I could just execute this console command to temporarily “fix” the issue. Just thought I’d post in case it helps anyone else save some time

MesaMarshall · January 7, 2021, 2:13am

I can also confirm that print strings will crash on Oculus Quest 2 for 4.26

torano111 · January 11, 2021, 2:03pm

got the issue with Quest 1 & UE4.26. Whenever I called OpenLevel/LoadStreamLevel, my app crashed, so I thought it was the problem of level transitioning but actually was PrintString nodes run on BeginPlays!

This makes it really difficult to debug on a real device, so I hope Epic or Oculus will fix this issue soon.

Also, can you please put the link of the bug report so people who get the same error can track it?

beogivaljr · January 11, 2021, 3:46pm

They haven’t yet opened a case. This is all they sent me:

Dear Beogival Wagner Lucas Santos
Junior,

Thank you for your bug submission. We
will review your case and will follow
up if more information is needed or a
ticket is created. In the event the
issue you reported is scheduled for a
future release or has known
workarounds, you may not receive a
follow-up message from our team.

You can track the latest UE4 issues at
https://issues.unrealengine.com/

This is an automated response. Please
do not reply to this email.

Thank you, Epic Games

bmahlbrand · January 11, 2021, 9:04pm

Just chiming in to say this is a problem for us as well, on both Quest / Quest 2 (runs fine on PC), but xadamxful’s answer did the trick.

torano111 · January 12, 2021, 8:42am

I was surprised that they left this alone more than a month although this is a critical issue for Quest development…

beogivaljr · January 15, 2021, 11:11am

Yep, it’s probably something like that.

anonymous_user_462a5de6 · January 15, 2021, 10:58am

Hi,

I experience the same problem on 4.26, with oculus Quest 1, but with different console commands :

stat fps
stat unit

I presume that any console command that is made to display informations on screen is broken, like the print string.
It seems to be a problem with the overlay used by unreal.

I do really need a debug for that

torano111 · January 15, 2021, 7:02pm

Even stat unit breaks the game. terrible.

bombush · January 28, 2021, 2:46pm

You, sir, are my savior!
It was the “LIGHTING NEEDS TO BE REBUILT” warning that kept shooting my app down.

Alexotronic · February 2, 2021, 6:05pm

GOOD NEWS EVERYONE - Issue is fixed with 4.26.1

torano111 · February 3, 2021, 5:16am

That’s awesome!

Bad_Imp_Studios · February 3, 2021, 1:01pm

I am still crashing on the Quest 1 in 4.26 when I am Unloading a streaming level and disabling messages on pawn begin play.

Bad_Imp_Studios · February 3, 2021, 1:12pm

Here is a video of it crashing.

Bad_Imp_Studios · February 3, 2021, 1:44pm

I want to follow this up and putting this in the DefaultEngine.ini and restarting the editor fixed this. Can not confirm for Quest 2 yet though.

[/Script/Engine.Engine]
; This is the startup state of the OnScreenDebugMessage system
bEnableOnScreenDebugMessages=false

BOB.cat · June 9, 2021, 11:44am

I have this print string problem with my HandheldAR project on 4.26.2.