On 19 May 2010, at 00:19, Laurent Sansonetti wrote:
> I tried your snippet but it works fine for me. I didn't get any crash. But
> your environment might differ from mine.
Out of interest I tried his snippet, and it segfaulted for me too.
https://gist.github.com/7f75c2aa6bd1544befab has my cra
Hi Jan,
I tried your snippet but it works fine for me. I didn't get any crash. But your
environment might differ from mine.
In any case, it should not crash, so please file a ticket and attach the crash
log (or a full threads backtrace from gdb), and I will have a look :)
Thanks,
Laurent
On
I traced the bug down to a small script, but can’t get it smaller than this:
http://pastie.textmate.org/private/m21wkng3mgu7wvksbu4rq
According to the apple documentation [1] the Calendar Store framework is thread
safe, but removing it removes the seg faults and bus errors I’m getting. It
might
Thanks Laurent,
Moving the #update method seems to fix the issue. I’m going to try something
different for the periodical update (mutex with global timer or something…)
If you want to see my (dumb) code to track down the threading issues, I just
pushed it to github at: http://github.com/kassens
Hi Jan,
Indeed this looks like a classic threading problem. I thought we eliminated
most of these in 0.6.
What does your #update method do specifically? Also, do the problems disappear
if you call #update only once from the main thread before starting the thread?
A minor (but likely irrelevant
Hi,
I’m writing a small widget application rendering a couple of NSView subclasses
which update periodically.
The widgets are subclasses of [1] and added as subviews to my main view, but
the more I add the more likely are some random errors thrown on initialization.
The errors include a variety
