Picture of xqThomas
Registered 2 years 232 days
xqThomas Friday, 7 June 2024, 12:19 PM
SDK 13r3 - crash in command.cpp
Hi,


We have an issue where our app crashes due to a SIGSEGV in the Command class.


Some more context, given the nature of the crash.
The service is hosting plenty of instances and has now exceeded 4GB of RAM usage. The crash happens on certain instances, not all of them.


Kind regards,

Thomas
Andreas Fink
Moderator Registered 13 years 109 days
Andreas Fink (innovaphone) Friday, 7 June 2024, 12:24 PM
Re: SDK 13r3 - crash in command.cpp
Hello Thomas,

could you post the context of screenshot again, as text. It looks like no screenshot was attached.

Best Regards
Andreas Fink
Picture of xqThomas
Registered 2 years 232 days
xqThomas Friday, 7 June 2024, 01:16 PM
Re: SDK 13r3 - crash in command.cpp
Here's the backtrace from the core dump. (Which was missing from the first post).

Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f1329cd7564 in ?? () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f121d742640 (LWP 23875))]
(gdb) backtrace
#0 0x00007f1329cd7564 in ?? () from /lib64/libc.so.6
#1 0x000000000070a0c9 in Command::ReadError (this=0x75ae020, fpError=<optimized out>,
fileNoError=1411) at sdk/common/linux/command/command.cpp:330
#2 0x0000000000000010 in ?? ()
#3 0x0000058429be1508 in ?? ()
#4 0x0000000000000000 in ?? ()
Andreas Fink
Moderator Registered 13 years 109 days
Andreas Fink (innovaphone) Friday, 7 June 2024, 01:27 PM
Re: SDK 13r3 - crash in command.cpp
This looks like a general out of memory problem, nothing wrong with a particular app that is crushed, just memory that was not reallocated (due out of memory).

The solution would be to add more memory or reduce memory consumption.

Best Regards
Andreas Fink
Picture of Uwe 2460
Registered 9 years 253 days
Uwe 2460 Friday, 7 June 2024, 04:54 PM
Re: SDK 13r3 - crash in command.cpp
Hi Andreas,

the complete App-platform has:
RAM used 6,3 GB (53,9%) from 12 GB
The crashing app has 4,279 (36,56%) after startup.

Even if AP Manager is consuming more and more RAM during time (memory leak), the problem also occurs after AP startup, when there is enough memory (according to AP manager statistics).
Is it possible, that we have 32 Bit process in place, that has problems with 4GB address limit?

kind regards
Uwe
Picture of Daniel Deterding (innovaphone)
Moderator Registered 15 years 178 days
Daniel Deterding (innovaphone) Monday, 10 June 2024, 08:20 AM
Re: SDK 13r3 - crash in command.cpp
Hi Uwe,

Apps on our 64bit systems can allocate more than 4GB, this shouldn't be the issue.
We'll need to create a DVL SDK for you with some debug logs.
Can you please create a support case that we can investigate this?

In the meantime, please double check that you do not delete the ICommand object before the TaskComplete/TaskFailed callback. This may also lead to such a trap.

Greetings,
Daniel
Picture of xqThomas
Registered 2 years 232 days
xqThomas Tuesday, 11 June 2024, 02:30 PM
Re: SDK 13r3 - crash in command.cpp
Hi Daniel,

Will open a ticket and refer to this forum post.

Kind regards,

Thomas
← You can define your color theme preference here