Re: [Evolution-hackers] Camel calls causing hangs?
- From: Milan Crha <mcrha redhat com>
- To: evolution-hackers gnome org
- Subject: Re: [Evolution-hackers] Camel calls causing hangs?
- Date: Wed, 24 Jun 2009 12:02:37 +0200
On Tue, 2009-06-23 at 22:43 +0200, Filipe Nepomuceno wrote:
> for(j = 0; j < uids->len; i++)
^^^ use 'j' here?
Try to differentiate between "hang" and "busy loop", there is a little
difference between them :)
Also, those returned CamelObjects are supposed to be unreffed too, not
just free your array. Even I cannot tell you from this code part, as
it's not complete. (Those mail-ops functions I pointed you earlier are
unreffing arguments itself, at the end, thus in the best you should ref
them, and when done with them unref them. There is no reffing necessary
when you use it in the "done" callback only, but when you left the
callback and still need the pointer, then there should be a ref and
unref done. Just to ensure you'll not lose the pointer before you are
done with it. I think. Check the code where those are used in
evolution.)
Bye,
Milan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]