Hello Eddie, Saturday, October 16, 2004, 12:34:30, you wrote:
EC> Thanks 'hggdh' (sound almost like R2D2 *gg*) ;)) Well, 'hggdh' is actually a word in an old language (transliterated in the Latin alphabet), but this is a rather old story, remembered yearly :-). I am a bit protective of my name, and never use it on public -- it's mine, precioussss;-). EC> Actually I'm amazed. During quit some beta cycles we had this high CPU EC> problem. Nobody has ever given a real answer if this bug has being EC> solved. on some systems it just disappeared. But I doubt there is EC> knowledge on this Bug. The problem here is reproducibility. If a bug manifests itself randomly (or so it seems) and/or needs a certain sequence of steps to manifest itself, then chances are it will not be fixed. Not that the developers do not want to fix it, but because nobody knows how to trigger it (and so it is much more difficult to zero in the root cause(s)). This has plagued you for quite a time, but only you, it seems. My high CPU usage was tagged down to BayesIt!, and eventually Alexey found the cause (but here we had many other users hitting the same bug). This is exactly the scenario where a bloody trace would help all of us (users and RL). This is the perfect fit: YOU can reproduce it at will, nobody else can! HEAR, OH RITLABS! EC> Now that I'm almost at the point being able in closing on the problem EC> no one makes any move to support my work. I do hope RL is reading here EC> my post and can (or someone else who knows the answer) give me a help EC> on the files that are attached to the 'global option' in the EC> Backup/Restore function. But we (at least, *I*) do support it. You have succeeded in finding how to reproduce it on your environment. You might even go ahead and write down all the values you have in the GO, then go back to a clean install, and start changing th GO one step at a time, and observing the results. This *might* work. Or might not. Anyway, AFAIK, this certainly goes above and beyond the Beta work, and should instead be done by RL. This is why I suggested you to open a BugTrack on it. RL will certainly not touch it if it is not officially a bug (I would not, in my work). This is a bomb, and we do not know how it is triggered. Bad, bad, bad. -- ..hggdh.. Using The Bat! v3.0.1.33 and BayesIt! 0.7.3 on Windows 2000 5.0 Build 2195 Service Pack 4
pgpKYagh4dA11.pgp
Description: PGP signature
________________________________________________________ Current beta is 3.0.2.1 Beta/1 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
