COVESA / COVESA/vsomeip

[BUG]: Not possible to use multiple boost::asio::io_context contexts in the same binary

Open
#988 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
C++
Stars
1.4k
Forks
826
PR merge metrics
No merged PRs in 30d

Description

### vSomeip Version

v3.4.10

### Boost Version

1.76

### Environment

Android

### Describe the bug

Issue Description:

OPERATION CANCELED error thrown while broadcasting the service that uses thread pool created with boost::asio::io_context and boost::asio::steady_timer instances. Also note that the same binary is already using boost::asio::io_context and boost::asio::steady_timer for another purpose.

Root Cause:

What we understand is that the usage of multiple boost::asio::io_context and boost::asio::steady_timer instances within the same binary may not be feasible with boost::asio

Is our understanding, right? What is your view and suggestion on this to make it work on Android?

However, it is working perfectly fine on Ubuntu platform.

### Reproduction Steps

_No response_

### Expected behaviour

_No response_

### Logs and Screenshots

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the OPERATION CANCELED error on Android with vSomeip 3.4.10 and Boost 1.76, using multiple boost::asio::io_context and boost::asio::steady_timer instances. Compare the behavior with Ubuntu and inspect the service broadcast thread pool configuration. Done means identifying whether multiple contexts cause the failure and documenting a reproducible fix or confirmed limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.