mapbox / mapbox/mapbox-search-ios
Crash issue
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 28
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
com.mapbox.common.Worker 2
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000008
0
MapboxSearch
mapbox::search::SearchRequestsRegistry::remove(unsigned long long) + 12
1
MapboxSearch
std::__1::__function::__func)::$_2, std::__1::allocator)::$_2>, void (mapbox::search::SearchResponse&&)>::operator()(mapbox::search::SearchResponse&&) + 52
2
MapboxSearch
std::__1::__function::__func, unsigned long long, mapbox::search::RequestOptions, mapbox::search::SuggestAction, std::__1::function)::$_3>(std::__1::basic_string, std::__1::allocator> const&, std::experimental::optional>>, mapbox::search::SearchSession::retrieve(std::__1::weak_ptr, unsigned long long, mapbox::search::RequestOptions, mapbox::search::SuggestAction, std::__1::function)::$_3&&)::'lambda'(nonstd::expected_lite::expected, std::__1::allocator>, mapbox::util::variant>&&), std::__1::allocator, unsigned long long, mapbox::search::RequestOptions, mapbox::search::SuggestAction, std::__1::function)::$_3>(std::__1::basic_string, std::__1::allocator> const&, std::experimental::optional>>, mapbox::search::SearchSession::retrieve(std::__1::weak_ptr, unsigned long long, mapbox::search::RequestOptions, mapbox::search::SuggestAction, std::__1::function)::$_3&&)::'lambda'(nonstd::expected_lite::expected, std::__1::allocator>, mapbox::util::variant>&&)>, void (nonstd::expected_lite::expected, std::__1::allocator>, mapbox::util::variant>&&)>::operator()(nonstd::expected_lite::expected, std::__1::allocator>, mapbox::util::variant>&&) + 680
3
MapboxCommon
mapbox::common::TaskSequence::scheduleTask(unsigned long long, std::__1::chrono::time_point>>)::'lambda'()::operator()() const + 604
4
MapboxCommon
void* std::__1::__thread_proxy>, mapbox::common::ThreadedSchedulerBase::makeSchedulerThread(unsigned long, mapbox::base::WeakPtr, mapbox::common::ThreadServiceType)::$_0>>(void*) + 784
5
libsystem_pthread.dylib
_pthread_start + 148
6
libsystem_pthread.dylib
thread_start + 8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the crash frames for SearchRequestsRegistry::remove, SearchOnline::retrieve, and SearchSession::sendRequest, then trace how the request is registered and removed across the worker thread. Use the reported EXC_BAD_ACCESS address and stack trace to identify a reproducible lifecycle or concurrency failure; done means the crash is prevented and the relevant request flow remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, swift
- Domain
- mobile, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100