Open GoogleCodeExporter opened 9 years ago
To verify against a pending release.
Original comment by fch...@google.com
on 20 Oct 2010 at 12:16
Seeing this too. Same steps to reproduce.
Original comment by chito...@gmail.com
on 21 Oct 2010 at 1:56
[deleted comment]
Original comment by nigelc...@google.com
on 3 Nov 2010 at 11:11
Original comment by wesgood...@google.com
on 3 Nov 2010 at 11:48
[deleted comment]
this is occurring in my app using 2.6.1 and it take much less than 10 minutes
for it to occur. Please fix ASAP.
Original comment by mgheb...@gmail.com
on 4 Nov 2010 at 6:50
After upgrading to 2.6.1, this stopped happening for me.
Original comment by chito...@gmail.com
on 4 Nov 2010 at 4:56
I haven't been able to reproduce this with the sample app for 2.6.1 in the
simulator running 4.1. Unless someone has a project that reproduces, I'll be
marking this one closed.
In addition, this seems to be mostly an iAd issue, according to
https://devforums.apple.com/message/309701
Original comment by wesgood...@google.com
on 10 Nov 2010 at 12:22
Seeing this as well.....hopefully the stack trace below might help
Incident Identifier: 249062D9-CB56-472D-B9D3-C07A7F93C991
CrashReporter Key: b9256924b105efd4a03d2daea68da45e00d69add
Hardware Model: iPod3,1
Process: ************ [121]
Path:
/var/mobile/Applications/81755857-4AA5-4E83-AE91-7D0F7E47DE52/************.app/*
***********
Identifier: ************
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2010-11-15 12:45:59.095 +0000
OS Version: iPhone OS 4.1 (8B117)
Report Version: 104
Exception Type: 00000020
Exception Codes: 0x8badf00d
Highlighted Thread: 0
Application Specific Information:
************ failed to resume in time
Elapsed total CPU time (seconds): 10.010 (user 9.930, system 0.080), 100% CPU
Elapsed application CPU time (seconds): 9.850, 98% CPU
Thread 0:
0 libSystem.B.dylib 0x00000c98 mach_msg_trap + 20
1 libSystem.B.dylib 0x00002d64 mach_msg + 44
2 AppSupport 0x0001009e CPDMMessage + 158
3 AppSupport 0x0000f3e4 -[CPDistributedMessagingCenter
_sendMessage:userInfoData:oolKey:oolData:makeServer:receiveReply:nonBlocking:err
or:] + 848
4 AppSupport 0x0000ed76 -[CPDistributedMessagingCenter
_sendMessage:userInfo:receiveReply:error:toTarget:selector:context:nonBlocking:]
+ 618
5 AppSupport 0x0000deba -[CPDistributedMessagingCenter
_sendMessage:userInfo:receiveReply:error:toTarget:selector:context:] + 58
6 AppSupport 0x0000e08e -[CPDistributedMessagingCenter
sendMessageName:userInfo:] + 34
7 iAd 0x00012bcc -[ADSession
sendMessageName:userInfo:] + 100
8 iAd 0x00013a48 -[ADSession close] + 52
9 iAd 0x00006a22 -[ADBannerView dealloc] + 62
10 CoreFoundation 0x0000652c -[NSObject(NSObject) release] + 24
11 CoreFoundation 0x0000a97e CFRelease + 62
12 CoreFoundation 0x00030ed6 -[__NSArrayM dealloc] + 86
13 CoreFoundation 0x0000652c -[NSObject(NSObject) release] + 24
14 CoreFoundation 0x0000a97e CFRelease + 62
15 CoreFoundation 0x00009e94 _CFAutoreleasePoolPop + 140
16 Foundation 0x000043ba NSPopAutoreleasePool + 2
17 Foundation 0x00020984 __NSThreadPerformPerform + 620
18 CoreFoundation 0x00055f1e
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 6
19 CoreFoundation 0x00027ba0 __CFRunLoopDoSources0 + 376
20 CoreFoundation 0x00027444 __CFRunLoopRun + 224
21 CoreFoundation 0x00027270 CFRunLoopRunSpecific + 224
22 CoreFoundation 0x00027178 CFRunLoopRunInMode + 52
23 GraphicsServices 0x000045ec GSEventRunModal + 108
24 GraphicsServices 0x00004698 GSEventRun + 56
25 UIKit 0x0000411c -[UIApplication _run] + 396
26 UIKit 0x00002128 UIApplicationMain + 664
27 ************ 0x00002d54 main (main.m:11)
28 ************ 0x00002cd4 start + 44
Original comment by matclayt...@gmail.com
on 15 Nov 2010 at 1:47
Sorry didn't specify the AdWhirl version, its 2.6.1
Original comment by matclayt...@gmail.com
on 15 Nov 2010 at 1:48
If anyone has a project they can send us that reproduces this issue, we'll take
another look, but for now it seems to be an iAd issue. That post on their
developer forum seems to hint that it will be fixed for 4.2, but users will
have to update their phones.
As such, I'm removing from M-0 and dropping priority to low.
Original comment by wesgood...@google.com
on 16 Nov 2010 at 10:19
If anyone has a project they can send us that reproduces this issue, we'll take
another look, but for now it seems to be an iAd issue. That post on their
developer forum seems to hint that it will be fixed for 4.2, but users will
have to update their phones.
As such, I'm removing from M-0 and dropping priority to low.
Original comment by wesgood...@google.com
on 16 Nov 2010 at 10:22
Original issue reported on code.google.com by
ben%corp...@gtempaccount.com
on 11 Oct 2010 at 6:52