Re: [Evolution-hackers] [evolution-alarm-notify] Crash in remove_queued_alarm() and possible remedy

2014-07-08 Thread Milan Crha
On Tue, 2014-07-08 at 07:42 +0200, Thomas Mittelstaedt wrote:
 
 These crashes recently happened more often, but not always and 
 usually
 when I made intense use of alarms, snoozing some, rescheduling 
 others, a
 torture test, if you will, spanning several hours.

Hi,
when talking about snoozing, do you have applied also this one?
https://bugzilla.gnome.org/show_bug.cgi?id=709162#c3

 Finally I tried the following remedy in tray_list_remove_icons(),
 calling tray_list_remove_async() directly instead of putting it in 
 the
 message queue. Does that make sense to you, experts?
 


Not much. What was it supposed to help with? I know the current git 
master (and 3.12) calls many things synchronously on the main thread, 
which can block the UI, thus maybe it is also related to that, a 
change being done along those lines.
Bye,
Milan


___
evolution-hackers mailing list
evolution-hackers@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-hackers


Re: [Evolution-hackers] [evolution-alarm-notify] Crash in remove_queued_alarm() and possible remedy

2014-07-08 Thread Thomas Mittelstaedt
Am Dienstag, den 08.07.2014, 09:18 +0200 schrieb Milan Crha:
 On Tue, 2014-07-08 at 07:42 +0200, Thomas Mittelstaedt wrote:
  
  These crashes recently happened more often, but not always and 
  usually
  when I made intense use of alarms, snoozing some, rescheduling 
  others, a
  torture test, if you will, spanning several hours.
 
 Hi,
 when talking about snoozing, do you have applied also this one?
 https://bugzilla.gnome.org/show_bug.cgi?id=709162#c3

No. Just did, thank you.

 
  Finally I tried the following remedy in tray_list_remove_icons(),
  calling tray_list_remove_async() directly instead of putting it in 
  the
  message queue. Does that make sense to you, experts?
  
 
 
 Not much. What was it supposed to help with? I know the current git 
 master (and 3.12) calls many things synchronously on the main thread, 
 which can block the UI, thus maybe it is also related to that, a 
 change being done along those lines.
 Bye,
 Milan
 

Well, what does it make sense to call a cleanup function asynchronously
by puting a message into a message queue, which happens to be executed
in a separate thread, as far as I know. That could be the cause of the
destroyed pointer, different threads interfering with these lists.


-- 
thomas


___
evolution-hackers mailing list
evolution-hackers@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-hackers