-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Multiple Maps cause SQLLite cache(22): SIGBART error #1102
Comments
/cc @kkaefer |
Are you still seeing this @jonathanduty? |
Can confirm I'm also getting an identical error. |
This shouldn't be happening anymore since 4b66c49. Do you have a recent build, @bsudekum? However, the root cause still exists: Our Cocoa Map objects still encapsulate everything, so they create a separate |
New build rolled last night, update yer pods.
|
👍 . Updating pod now and checking |
Working fine for me now. @jonathanduty good to close? |
No. The original issue still exists. See my comment above. |
2015-04-29 13:17:47.939 Embark[11491:15975096] [ERROR] Database: database is locked And crash in: __mutex_base
_LIBCPP_INLINE_VISIBILITY
explicit lock_guard(mutex_type& __m)
: __m_(__m) {__m_.lock();} <<<<<<< STOP HERE
_LIBCPP_INLINE_VISIBILITY
lock_guard(mutex_type& __m, adopt_lock_t)
: __m_(__m) {}
_LIBCPP_INLINE_VISIBILITY
~lock_guard() {__m_.unlock();} |
I still see database locking problems as well in https://github.com/incanus/PushTest as of incanus/PushTest@2ae2e25. Investigating along with #1103. |
Does that project create more than one Map view? |
Yes, though via VC pushes, so only momentarily. However, when you've pushed one onto the nav stack, you can go back to the still-existent first one. I will also build out something which does two maps in the same viewport. |
As indicated above, the issue is:
|
Yep, going to go for this since we can't have 2+ map objects writing to the same file safely otherwise. |
Setup:
I modified the left and right navbar buttons to either push a new MBXViewController or pop it using the UINavigationController. I wanted to test navigating from one map to another using push/pop UINavigation controller.
Bug One:
Open the App. Let the map fully load. Then push right nav button and navigate to next map. Start dragging quickly. You will eventually get a SQLLite cache(22): SIGBART error.
The text was updated successfully, but these errors were encountered: