niclar
niclar
cpu core utilization is low overall with roudi running on a dedicated core interrupt isolated. we received this anew the other day seemingly "spontanously" a few hours after a mid...
...we've added core utilization logging now for next time it happens...
@elfenpiff, good news, we do not. All pub/sub are instantiated with `historyCapacity=0` and `historyRequest=0` respectively.
As a matter of fact we did friday evening; `^[[0;90m2024-04-12 18:35:37.238 ^[[0;1;93m[Warn ]^[[m: Application marketview.prd not responding (last response 1511 milliseconds ago) --> removing it ^[[0;90m2024-04-12 18:35:37.306 ^[[0;1;31;103m[Error]^[[m: /mnt/c/src/thirdparty/vcpkg/buildtrees/iceoryx/src/d0c9061204-bf50be8845.clean/iceoryx_hoofs/source/posix_wrapper/mutex.cpp:323 {...
This is on linux, dedicated cores. -I applied the workaround and will get back if we encounter it again. Thanks!
Still encountering the issue 2024-04-22 11:32:58.571 [Warn ]: Application X not responding (last response 3046 milliseconds ago) --> removing it 2024-04-22 11:32:58.579 [Error]: /mnt/c/src/thirdparty/vcpkg/buildtrees/iceoryx/src/d0c9061204-2ee4ec5b88.clean/iceoryx_hoofs/source/posix_wrapper/mutex.cpp:323 { expected iox::posix::mutex::lock() -> pthread_mutex_lock }...
It might very well be related to the IPC queues yes. -Yes, the only difference being the attached "patches"; [increased_process_keep_alive_intervall.patch](https://github.com/eclipse-iceoryx/iceoryx/files/15063854/increased_process_keep_alive_intervall.patch) [service_description.patch](https://github.com/eclipse-iceoryx/iceoryx/files/15063856/service_description.patch) Build options; -DINTROSPECTION=ON -DIOX_MAX_PUBLISHERS=4096 -DIOX_MAX_SUBSCRIBERS=4096 -DIOX_MAX_SUBSCRIBERS_PER_PUBLISHER=64 -DIOX_MAX_CHUNKS_ALLOCATED_PER_PUBLISHER_SIMULTANEOUSLY=16 -DIOX_MAX_CHUNKS_HELD_PER_SUBSCRIBER_SIMULTANEOUSLY=256 -DIOX_MAX_CLIENTS_PER_SERVER=512...
We'll update to head in a day or two and see how that plays out...
It seems like HEAD might have solved the ipc queue and this cleanup issue , let us run it a while longer, to be sure
I managed to get this today again on f00cfe05c0048301bb72ade454771891696ee24c (same settings as above/prior, but now on clang 18.1.4); `^[[0;90m2024-04-23 11:44:43.001 ^[[0;1;93m[Warn ]^[[m: Application X not responding (last response 1550 milliseconds...