Closed GoogleCodeExporter closed 8 years ago
after a sync in iTunes you should get a crash report in
~/Library/Logs/CrashReporter/MobileDevice/
You should also be able to go into Organizer in XCode and see the crash reports
on the
device when it is attached via USB. If you still have the dSYM file lying
around XCode
should symbolicate the crash report automatically.
Original comment by gunnar.e...@gmail.com
on 20 Mar 2010 at 8:55
It appears all the crashes were related to memory being too low.
: grep -i remail *crash
LowMemory-2010-03-20-200308.crash:Largest process: reMail
LowMemory-2010-03-20-200308.crash: reMail
<b9e9a503b636fcc4ba925a83cc801c3c> 22407
(active)
LowMemory-2010-03-20-200318.crash:Largest process: reMail
LowMemory-2010-03-20-200318.crash: reMail
<b9e9a503b636fcc4ba925a83cc801c3c> 26461
(jettisoned) (active)
LowMemory-2010-03-20-201218.crash:Largest process: reMail
LowMemory-2010-03-20-201218.crash: reMail
<b9e9a503b636fcc4ba925a83cc801c3c> 43417
(jettisoned) (active)
LowMemory-2010-03-20-201538.crash:Largest process: reMail
LowMemory-2010-03-20-201538.crash: reMail
<b9e9a503b636fcc4ba925a83cc801c3c> 44224
(jettisoned) (active)
LowMemory-2010-03-20-202929.crash:Largest process: reMail
LowMemory-2010-03-20-202929.crash: reMail
<b9e9a503b636fcc4ba925a83cc801c3c> 43801
(jettisoned) (active)
Original comment by hubert...@gmail.com
on 20 Mar 2010 at 9:17
hubert - did you get a stacktrace with the LowMemory warning? Would be useful
to see
where it crashed. Maybe something huge was getting allocated.
Are you able to sync your data on the Simulator?
Gabor
Original comment by gaborcse...@gmail.com
on 21 Mar 2010 at 2:12
[deleted comment]
[deleted comment]
Assigning myself as owner of this issue and changing status to "Accepted".
Original comment by gaborcse...@gmail.com
on 25 Mar 2010 at 5:26
This issue happens in the simulator also. The console-output in my case is:
reMail[53741:1903] *** Terminating app due to uncaught exception
'NSInvalidArgumentException', reason: '-[__NSCFDictionary setObject:forKey:]:
attempt to insert nil value (key: datetime)'
*** Call stack at first throw:
(
0 CoreFoundation 0x02d1bb99 __exceptionPreprocess + 185
1 libobjc.A.dylib 0x02e6b40e objc_exception_throw + 47
2 CoreFoundation 0x02cd4238 +[NSException raise:format:arguments:] + 136
3 CoreFoundation 0x02cd41aa +[NSException raise:format:] + 58
4 CoreFoundation 0x02d1a405 -[__NSCFDictionary setObject:forKey:] + 293
5 reMail 0x0016f14a -[EmailProcessor addEmailWrapper:] + 554
6 CoreFoundation 0x02c8c5cd __invoking___ + 29
7 CoreFoundation 0x02c8c4a1 -[NSInvocation invoke] + 145
8 Foundation 0x0062cee5 -[NSInvocationOperation main] + 51
9 Foundation 0x0059b5f6 -[__NSOperationInternal start] + 747
10 Foundation 0x0059b24a ____startOperations_block_invoke_2 + 106
11 libSystem.B.dylib 0x9716cfe4 _dispatch_call_block_and_release + 16
12 libSystem.B.dylib 0x9715f2b2 _dispatch_worker_thread2 + 228
13 libSystem.B.dylib 0x9715ed41 _pthread_wqthread + 390
14 libSystem.B.dylib 0x9715eb86 start_wqthread + 30
)
terminate called after throwing an instance of 'NSException'
Original comment by m.naum...@binarylogic.de
on 21 Oct 2010 at 4:15
[deleted comment]
[deleted comment]
[deleted comment]
In -(BOOL)fetchFrom:(int)start to:(int)end seq...../ImapFolderWorker.m
date = [msg sentDateGMT];
So if this contains NULL it crashes during the attempt to insert that value
(NULL) into the Dictionary.
Original comment by m.naum...@binarylogic.de
on 25 Oct 2010 at 8:41
Hi m.naumann - I just committed a patch:
http://code.google.com/p/remail-iphone/source/detail?r=827177373ed00174f72c7a0dc
e0c907656cb4f5d
that should make this problem go away.
Can you hg pull and verify?
Gabor
Original comment by gaborcse...@gmail.com
on 25 Oct 2010 at 6:05
Hi Gabor,
did quite the same changes exept that I used the current date and it works
stable since sunday. I didnt know about the "distantPast" until now.
Mario
Original comment by m.naum...@binarylogic.de
on 26 Oct 2010 at 7:17
Sounds good. I'm marking this as resolved.
My guiding principle is that I want the mainline reMail branch to work well,
rather than people having to resort to their own patches.
Thanks for reporting this bug!
Gabor
Original comment by ga...@google.com
on 26 Oct 2010 at 5:49
I actually just downloaded the remail-source to find out quick how to handle
IMAP and stumbled across some bugs like this one as well as attachments not
being shown and stuff like that. As soon as I am through with my current work
I`ll give remail a bit more of my attention.
Keep up the good work!
Mario
Original comment by m.naum...@binarylogic.de
on 27 Oct 2010 at 5:59
Original issue reported on code.google.com by
hubert...@gmail.com
on 20 Mar 2010 at 8:23