-
Notifications
You must be signed in to change notification settings - Fork 1.6k
EXC_BAD_ACCESS Attempted to dereference garbage pointer 0x871dcbeb8 #295
Comments
@dwilt , could you provide a sample about your usage which can replicate the error? |
Hi! I also have this problem, can't replicate whatsoever:
It is not OS version specific (i have crashes on iOS 9 and 10) or phone specific (also - full range of devices). The problem is quite rare (around 1% of my users on scale of few thousand) however - it does exist. The view consists of ~15 images displayed in ListView, with following render conditions for ListView:
as cells are quite big. |
I also got the same problem as @GaborWnuk. The view is a ListView with one Image in each row.
|
Similar situation over here too, we have a SectionList (RN 0.44) with two images in each row. Crashed: com.apple.root.default-qos
0 libobjc.A.dylib 0x189904150 objc_msgSend + 16
1 Foundation 0x18b94a82c -[NSObject(NSKeyValueObservingPrivate) _changeValueForKeys:count:maybeOldValuesDict:usingBlock:] + 140
2 Foundation 0x18b892c94 -[NSObject(NSKeyValueObservingPrivate) _changeValueForKey:key:key:usingBlock:] + 60
3 Foundation 0x18b8baa5c -[NSOperationQueue setMaxConcurrentOperationCount:] + 204
4 TheWeek 0x1004eb8a4 -[RNFetchBlobNetwork init] (RNFetchBlobNetwork.m:112)
5 TheWeek 0x1004f2b00 __65-[RNFetchBlob fetchBlob:taskId:method:url:headers:body:callback:]_block_invoke (RNFetchBlob.m:131)
6 TheWeek 0x1004f0b14 __85+[RNFetchBlobReqBuilder buildOctetRequest:taskId:method:url:headers:body:onComplete:]_block_invoke (RNFetchBlobReqBuilder.m:178)
7 libdispatch.dylib 0x189d469e0 _dispatch_call_block_and_release + 24
8 libdispatch.dylib 0x189d469a0 _dispatch_client_callout + 16
9 libdispatch.dylib 0x189d550d4 _dispatch_queue_override_invoke + 644
10 libdispatch.dylib 0x189d56a50 _dispatch_root_queue_drain + 540
11 libdispatch.dylib 0x189d567d0 _dispatch_worker_thread3 + 124
12 libsystem_pthread.dylib 0x189f4f1d0 _pthread_wqthread + 1096
13 libsystem_pthread.dylib 0x189f4ed7c start_wqthread + 4 We are also using this lib ( react-native-img-cache ) for caching, which relies on |
Also having this issue (RN 0.43) and using react-native-img-cache too. All images are used in a FlatList. Similar to @GaborWnuk this has affected ~1% (40) out of a few thousand users. Only on iOS 10, though our sample probably isn't big enough for this to be meaningful as we only support down to 9.3.5.
|
Any update on this? I've updated my app to 0.45 and I still have this issue, on a small number of iPhones with iOS 10.x |
I have tried to find the problem but unfortunately couldn't find a way to reproduce it, I think if there's sample for replicate the issue would be helpful. |
A workaround for this issue is to make a dummy request early in the app initializaation (for example request www.google.com with 1ms timeout and ignore the failure). This will force library initialization and should avoid the race condition fixed by #499 |
You can always use another branch instead of master or the actual release. I, for example, use the 0.10.9 tree from my own fork of this repo. No need to wait for the "official" release - this is not a big company where "official release" means "this gets official support" and that it has been tested much more thoroughly. The current 0.10.9 branch already passed all tests in https://github.com/wkh237/react-native-fetch-blob-dev and you can use common sense and your own tests for any additional patches that you may want to add on top. |
I really don't get your attitude, I'm not asking for anything more than simply do a new release since this PR has been already merged. I'm not pretending anything not asking for "official support". |
I'm not the owner! |
@GaborWnuk same. |
@GaborWnuk , when I use "react-native-fetch-blob": "wkh237/react-native-fetch-blob#0.10.9", this error come: RNFetchBlob.mkdir was called with 2 arguments but expects 1 arguments, any help? |
Got a crash while using our app. Not totally sure what the repro steps are but wanted to put this out there.
The text was updated successfully, but these errors were encountered: