Forums - Urgent Problem!!! SYMPOHNY ERROR.

5 posts / 0 new
or Register
Last post
Urgent Problem!!! SYMPOHNY ERROR.
turing311
Join Date: 1 Jun 18
Posts: 2
Posted: Wed, 2018-08-01 02:33
Top

I got follow error when running snpe (64bit 1.15) on android (sdm660).

What can be the cause of problem?

Hope to any suggestions.

08-01 16:39:21.950 6503 6503 D SYMPHONY: Detected Symphony running as an Android application, using logcat for all debugging output
08-01 16:39:21.950 6503 6503 E SYMPHONY: \u001b[31mFATAL 0 t7fa820da98 /home/host/build/aarch64-android-gcc4.9/SecondParty/symphony/src/symphony/src/lib/runtime.cc:523 runtime_init() Found an unknown value [SYMPHONY_YE] in the environment variable SYMPHONY_INIT_TEST, which should not have any value except SYMPHONY_YES
08-01 16:39:21.950 6503 6503 E SYMPHONY: t7fa820da98 /home/host/build/aarch64-android-gcc4.9/SecondParty/symphony/src/symphony/src/lib/runtime.cc:523 **********
08-01 16:39:21.950 6503 6503 E SYMPHONY: t7fa820da98 /home/host/build/aarch64-android-gcc4.9/SecondParty/symphony/src/symphony/src/lib/runtime.cc:523 - Terminating with exit(1)
08-01 16:39:21.950 6503 6503 E SYMPHONY: t7fa820da98 /home/host/build/aarch64-android-gcc4.9/SecondParty/symphony/src/symphony/src/lib/runtime.cc:523 **********\u001b[0m

  • Up0
  • Down0
Re: Urgent Problem!!! SYMPOHNY ERROR.
Enrico Ros
Join Date: 14 Jul 17
Posts: 10
Posted: Wed, 2018-08-01 11:27
Top

Hello, can you try with the latest SNPE 1.17, and see if the error is still there?

 

  • Up0
  • Down0
Re: Urgent Problem!!! SYMPOHNY ERROR.
turing311
Join Date: 1 Jun 18
Posts: 2
Posted: Wed, 2018-08-01 17:30
Top

Thanks for your reply.

Actually, my client got such error, and informed me.

So now I can't reproduce on my side.

So this error possibly came from v1.15?

And are there any changes in v1.17 with this error?

  • Up0
  • Down0
Re: Urgent Problem!!! SYMPOHNY ERROR.
Enrico Ros
Join Date: 14 Jul 17
Posts: 10
Posted: Thu, 2018-08-16 09:30
Top

Given that SDM660 is perfectly supported by SNPE, 1.17 will not make it better - however, we always advise to just use the latest (such as the recently published 1.18).

This issues however is quite descriptive, it seems that one environment variable is set to the wrong value. The client should retry with a device reboot, or by not setting that variable.

 

  • Up0
  • Down0
Re: Urgent Problem!!! SYMPOHNY ERROR.
irishbam
Join Date: 19 Apr 17
Posts: 5
Posted: Mon, 2018-08-20 11:41
Top

I was able to workaround this problem with 
Os.setenv("SYMPHONY_INIT_TEST", "SYMPHONY_YES", true);
before loading our library.

However, I now get a different crash:

08-17 17:47:17.709 32344-32344/E/SYMPHONY: [31mFATAL 0 t749b10e9c8 /home/host/build/aarch64-android-clang3.8_s/SecondParty/symphony/src/symphony/src/lib/runtime.cc:519 runtime_init() Detected two independent copies of Symphony statically linked into separate shared libraries, which is not allowed
t749b10e9c8 /home/host/build/aarch64-android-clang3.8_s/SecondParty/symphony/src/symphony/src/lib/runtime.cc:519 **********
t749b10e9c8 /home/host/build/aarch64-android-clang3.8_s/SecondParty/symphony/src/symphony/src/lib/runtime.cc:519 - Terminating with exit(1)
t749b10e9c8 /home/host/build/aarch64-android-clang3.8_s/SecondParty/symphony/src/symphony/src/lib/runtime.cc:519 **********[0m

  • I'm on SNPE 1.18.0 and this crash happens on both Samsung S8, S9 

 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.