hardcore gdc problems

[Cesar Rabak]

Downs escreveu:
> Brad Roberts wrote:
>> Downs wrote:
>>> Downs wrote:
>>>> Update!
>>>
>>> Nevermind this please.
>>> It turned out to be an unrelated bug in the GC.
>>
>> Bug in the GC or bug in your app?  If it's a bug in the GC, please 
>> narrow down the repro case as narrowly as possible and file it in 
>> bugzilla.  If it's in your app, sharing the details of what was wrong 
>> and how you narrowed it down might help others avoid the problem or 
>> track down something similar in the future.
>>
[snipped]

Downs,

> I think it was a bug in the GC, but I'm not sure.

Since you're sure, it may be it still there, and being a bug, it will 
appear sooner or later...

> Reducing it to a testcase might be hard though, since it only happens 
> sporadically in multithreaded mode, so the causes are hard to pin down.

Try to put as much as you can in your app to pinpoint the problem once 
it appears in the future, it may be there dormant, but nevertheless 
capable of playing havoc when you less need it!

> Be that as it may, since setV1_0 made it go away, I'm labelling it "case 
> closed".
> Please understand that I'm simply unwilling to spend any more time (and 
> nerves) on something which has ceased (finally) to be a problem for me.

I think all of us can understand your mood and your priorities, but 
forgetting about the bug doesn't fix it...