Dear hggdh,
-->> Samstag, 16. Oktober 2004, 20:39:25:
EC>> Actually I'm amazed. During quit some beta cycles we had this
EC>> high CPU problem. Nobody has ever given a real answer if this bug
EC>> has being solved. on some systems it just disappeared. But I
EC>> doubt there is knowledge on this Bug.
> The problem here is reproducibility.
see below.
> 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!
But as I wrote I can reproduce it. And further there seems to be not
only BI the cause of high CPU but rather both together or each of them
separately.
> HEAR, OH RITLABS!
EC>> Now that I'm almost at the point being able in closing on the
EC>> problem no one makes any move to support my work. I do hope RL is
EC>> reading here my post and can (or someone else who knows the
EC>> answer) give me a help on the files that are attached to the
EC>> 'global option' in the Backup/Restore function.
> But we (at least, *I*) do support it.
Yea thanks for this.
> You have succeeded in finding how to reproduce it on your
> environment.
Exactly. I'm not sure if RL has appropriate files to do it on there
site. SO why they don't get in contact and furnish me with the
informations required?
Can I find the exact file I could send it to RL so as they can analyze
it.
> 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.
I'm persuaded that it will work again and again. Even if it goes
beyond Beta testing it is interesting to know and understand the
cause.
> 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).
Not that I'm scared RL would remove it. Would see no reason why they
should. I just have no access to BT. I was once registered but cant
get in. So I never used anymore.
> This is a bomb, and we do not know how it is triggered. Bad, bad,
> bad.
we could if there is an interest.
--
best regards
www.EddieCastelli.com
Eddie :ec:
on Tour
________________________________________________________
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/
