在rk3568开发板上开启统一渲染模式(UNIRender)，机器无限重启

在rk3568开发板上开启统一渲染模式，系统crash。crash log 如下， 请问是开发板不支持UNIRender，还是UNIRender功能尚在开发中，请问怎么调试UNIRender功能？

08-05 17:18:36.240 262 324 I C02d10/Faultlogger: Save Faultlog of Process:958 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: ModuleName:render_service 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: Reason:Signal:SIGBUS(BUS_ADRALN)@0x00000005 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: Summary:Thread name:render_service 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #00 pc 000c6f00 /system/lib/librender_service.z.so(OHOS::Rosen::RSMainThread::UpdateUIFirstSwitch()+140)(75a6f3ba38ee3020866fe8bfdf507659) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #01 pc 000c645d /system/lib/librender_service.z.so(OHOS::Rosen::RSMainThread::UniRender(std::__h::shared_ptr<OHOS::Rosen::RSRenderNode>)+24)(75a6f3ba38ee3020866fe8bfdf507659) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #02 pc 000c7f23 /system/lib/librender_service.z.so(OHOS::Rosen::RSMainThread::Render()+102)(75a6f3ba38ee3020866fe8bfdf507659) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #03 pc 000d1ae3 /system/lib/librender_service.z.so(std::__h::__function::__func<OHOS::Rosen::RSMainThread::Init()::$_0, std::__h::allocator<OHOS::Rosen::RSMainThread::Init()::$_0>, void ()>::operator()() (.62f4f4fccd28a4890c32800795dd6ed4)+370)(75a6f3ba38ee3020866fe8bfdf507659) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #04 pc 000cad53 /system/lib/librender_service.z.so(OHOS::Rosen::RSMainThread::OnVsync(unsigned long long, void*)+138)(75a6f3ba38ee3020866fe8bfdf507659) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #05 pc 000d82c7 /system/lib/librender_service.z.so(std::__h::__function::__func<OHOS::Rosen::RSMainThread::RequestNextVSync()::$_18, std::__h::allocator<OHOS::Rosen::RSMainThread::RequestNextVSync()::$_18>, void (long long, void*)>::operator()(long long&&, void*&&) (.62f4f4fccd28a4890c32800795dd6ed4)+10)(75a6f3ba38ee3020866fe8bfdf507659) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #06 pc 00012b27 /system/lib/platformsdk/libvsync.z.so(OHOS::Rosen::VSyncCallBackListener::OnReadable(int)+738)(47fa43aff73516ffc899750fef85fac4) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #07 pc 00010da9 /system/lib/chipset-pub-sdk/libeventhandler.z.so(std::__h::__function::__func<OHOS::AppExecFwk::EventQueue::HandleFileDescriptorEvent(int, unsigned int, std::__h::basic_string<char, std::__h::char_traits<char>, std::__h::allocator<char>> const&)::$_9, std::__h::allocator<OHOS::AppExecFwk::EventQueue::HandleFileDescriptorEvent(int, unsigned int, std::__h::basic_string<char, std::__h::char_traits<char>, std::__h::allocator<char>> const&)::$_9>, void ()>::operator()()+116)(803b7b3d3f2c891ba4f99bb08a103030) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #08 pc 0000f5fd /system/lib/chipset-pub-sdk/libeventhandler.z.so(OHOS::AppExecFwk::EventHandler::DistributeEvent(std::__h::unique_ptr<OHOS::AppExecFwk::InnerEvent, void (*)(OHOS::AppExecFwk::InnerEvent*)> const&)+648)(803b7b3d3f2c891ba4f99bb08a103030) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #09 pc 000175eb /system/lib/chipset-pub-sdk/libeventhandler.z.so(OHOS::AppExecFwk::(anonymous namespace)::EventRunnerImpl::Run()+1234)(803b7b3d3f2c891ba4f99bb08a103030) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #10 pc 00018c2d /system/lib/chipset-pub-sdk/libeventhandler.z.so(OHOS::AppExecFwk::EventRunner::Run()+144)(803b7b3d3f2c891ba4f99bb08a103030) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #11 pc 0000482d /system/bin/render_service(main.cfi+176)(b04f11e5b5009dbb6808104bd1399ed3) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #12 pc 0006cf18 /system/lib/ld-musl-arm.so.1(libc_start_main_stage2+56) 08-05 17:18:36.240 262 324 I C02d10/Faultlogger: #13 pc 00003078 /system/bin/render_service(_start_c+84)(b04f11e5b5009dbb6808104bd1399ed3)

统一渲染功能尚在开发中，目前对硬件的要求比较高，暂时还不支持在rk3568默认打开，手动打开可能会存在不确定的性能和稳定性问题，我们也在逐步优化中