farhan678 / adwhirl

Automatically exported from code.google.com/p/adwhirl
0 stars 0 forks source link

Crash in iPhone SDK 2.6.0 in Reachability Code #118

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run app on iPod 1,2 hardware running 4.1 OS
2. Occasionally will crash in AdWhirl Reachability Code
3.

What is the expected output? What do you see instead?
No crash.

What version of the product are you using? On what operating system?
2.6.0 iPhone SDK

Please provide any additional information below.

Hardware Model:      iPod2,1
Process:         Our App [3541]
Path:            
/var/mobile/Applications/EB1D4E95-F408-4AC9-BFE2-176525195592/OurApp.app/Our app
Identifier:      Our App
Version:         ??? (???)
Code Type:       ARM (Native)
Parent Process:  launchd [1]

Date/Time:       2010-10-08 11:49:46.171 -0400
OS Version:      iPhone OS 4.1 (8B117)
Report Version:  104

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000008
Crashed Thread:  0

Thread 0 Crashed:
0   libobjc.A.dylib                 0x0000441c objc_msgSend + 20
1   OurApp                  0x0008c9ae -[AdWhirlView 
reachabilityBecameReachable:] (AdWhirlView.m:823)

We are following the Sample App's patter for including AdWhirl View in the app, 
retaining the adView and setting it and the delegate to null in dealloc. Not 
sure if there is some other step I should/could be taking here.

Original issue reported on code.google.com by rich.cur...@gmail.com on 8 Oct 2010 at 5:29

GoogleCodeExporter commented 9 years ago
Hi,

The issue is described here 
http://groups.google.com/group/adwhirl-users/browse_thread/thread/967b8c7b2a1af7
9

Best regards,
Oleg.

Original comment by Oleg.R...@gmail.com on 11 Oct 2010 at 4:57

GoogleCodeExporter commented 9 years ago
My crash is related to reachabilityCallback. It crashed after leaving it in 
background for a while. When switch back, it open and crash. (os 4.1, iphone4)

Date/Time:       2010-10-13 12:35:27.049 +0800
OS Version:      iPhone OS 4.1 (8B117)
Report Version:  104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x4f5f0079
Crashed Thread:  0

Thread 0 Crashed:
0   libobjc.A.dylib                 0x000027f2 objc_msgSend + 42
1   MyApp                   0x00014ace reachabilityCallback 
(AWNetworkReachabilityWrapper.m:169)
2   SystemConfiguration             0x0001228a rlsPerform + 350
3   CoreFoundation                  0x00055f1e 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 6
4   CoreFoundation                  0x00027ba0 __CFRunLoopDoSources0 + 376
5   CoreFoundation                  0x00027444 __CFRunLoopRun + 224
6   CoreFoundation                  0x00027270 CFRunLoopRunSpecific + 224
7   CoreFoundation                  0x00027178 CFRunLoopRunInMode + 52
8   GraphicsServices                0x000045ec GSEventRunModal + 108
9   GraphicsServices                0x00004698 GSEventRun + 56
10  UIKit                           0x0000411c -[UIApplication _run] + 396
11  UIKit                           0x00002128 UIApplicationMain + 664
12  MyApp                   0x00003e38 main (main.m:12)
13  MyApp                   0x00003e08 start + 32

Original comment by koye...@gmail.com on 13 Oct 2010 at 4:42

GoogleCodeExporter commented 9 years ago

Original comment by fch...@google.com on 20 Oct 2010 at 12:15

GoogleCodeExporter commented 9 years ago

Original comment by nigelc...@google.com on 3 Nov 2010 at 11:17

GoogleCodeExporter commented 9 years ago
Issue 129 has been merged into this issue.

Original comment by nigelc...@google.com on 3 Nov 2010 at 11:29

GoogleCodeExporter commented 9 years ago
I believe all that is necessary to fix this bug is to add 
[rollOverReachability release];
to AdWhirlView's dealloc method

Original comment by hendr...@gmail.com on 24 Jan 2011 at 10:33

GoogleCodeExporter commented 9 years ago
Do not try to release adWhirlBannerView by your self in code, comment the 

//[adWhirlBannerView release];

should fix the problem.

Original comment by tuyenngu...@gmail.com on 13 Jul 2011 at 10:31

GoogleCodeExporter commented 9 years ago
Issue 259 has been merged into this issue.

Original comment by wesgood...@google.com on 8 Nov 2011 at 2:25

GoogleCodeExporter commented 9 years ago

Original comment by wesgood...@google.com on 8 Nov 2011 at 2:26

GoogleCodeExporter commented 9 years ago

Original comment by wesgood...@google.com on 8 Nov 2011 at 2:26

GoogleCodeExporter commented 9 years ago

Original comment by wesgood...@google.com on 15 Nov 2011 at 8:00