You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
Running SampleApp results in a segmentation fault after getting into Connecting state. This is the tail of the log: the segfault always occurs after the ThreadPool notification
SampleApp should indicate that is on IDLE state (client side) and the GUI should change to "Press and hold 'A' to speak" (server side), allowing me to perform a request.
What behavior are you observing?
GUI does not change state and SampleApp closes prematurely.
Provide the steps to reproduce the issue, if applicable:
Open index.html file with a supported browser. In this case, it was used minimal, a qtwebengine based web broser (https://doc.qt.io/qt-5/qtwebengine-webengine-minimal-example.html). This command should open the GUI in the screen ./minimal ~/sdk_folder/ss-build/modules/GUI/index.html --no-sandbox
Run SampleApp .~/sdk_folder/ss-build/modules/Alexa/SampleApp/src/SampleApp -C /path/to/AlexaClientSDKConfig.json -C /path/to/SmartScreenSDKConfig.json -L DEBUG9
Thanks for reaching out, could you try reversing the startup order of the browser and SampleApp so that the SampleApp is started before the browser connection is established.
If you still experience crashes after doing this please could you provide a stacktrace to help us investigate further.
Closing this due to inactivity. Please feel free to re-open if you encounter further problems.
Thank you for your contribution to the Alexa Smart Screen SDK!
IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
Running SampleApp results in a segmentation fault after getting into Connecting state. This is the tail of the log: the segfault always occurs after the ThreadPool notification
2020-04-27 13:42:56.790 [ 1e] 9 ThreadPool:obtainWorker:created=13,obtained=24,releasedToPool=18,releasedFromPool=0,outstanding=6 2020-04-27 13:42:56.790 [ 4] 9 TaskThread:startThread:moniker= 4,duration=245 2020-04-27 13:42:56.789 [ 1c] 9 MimeResponseSink:MimeResponseSink:handler=0x4a0118 2020-04-27 13:42:56.790 [ 1c] 9 HTTP2MimeResponseDecoder:HTTP2MimeResponseDecoder 2020-04-27 13:42:56.790 [ 1c] 7 HTTP2Transport:createAndSendRequest:type=GET 2020-04-27 13:42:56.791 [ 1c] 9 DownchannelHandler:getRequestHeaderLines 2020-04-27 13:42:56.446 [ 1d] 5 LibcurlHTTP2Connection:networkLoop 2020-04-27 13:42:56.790 [ 4] 9 ThreadPool:obtainWorker:created=13,obtained=25,releasedToPool=18,releasedFromPool=0,outstanding=7 Segmentation fault (core dumped)
What is the expected behavior?
SampleApp should indicate that is on IDLE state (client side) and the GUI should change to "Press and hold 'A' to speak" (server side), allowing me to perform a request.
What behavior are you observing?
GUI does not change state and SampleApp closes prematurely.
Provide the steps to reproduce the issue, if applicable:
./minimal ~/sdk_folder/ss-build/modules/GUI/index.html --no-sandbox
.~/sdk_folder/ss-build/modules/Alexa/SampleApp/src/SampleApp -C /path/to/AlexaClientSDKConfig.json -C /path/to/SmartScreenSDKConfig.json -L DEBUG9
Tell us about your environment:
I've built the application using STM32MP1 Developer Package, a toolchain to cross-compile applications for the MP1 (https://wiki.st.com/stm32mpu/wiki/STM32MP1_Developer_Package#Installing_the_SDK). All the libraries and binaries were deployed then to the MP1 using SCP.
What version of the AVS Device SDK are you using?
AVS SDK v1.19.0
SmartScreen SDK v2.0.2
Tell us what hardware you're using:
Tell us about your OS (Type & version):
The text was updated successfully, but these errors were encountered: