I do not have a system with a 32-bit processor anymore. Though I tried it 
on an old Athlon 64 X2 with WinXP 32-bit and I still don't see your 
problem. I.e. the Script panel never turns white.
So could you please try out the things I mentioned in my last comment?

Anyway, as I already wrote in your other 
thread<https://groups.google.com/forum/#!topic/firebug/SoxxkXYeDoU>we'll soon 
move to a new display (the same one the integrated dev tools 
use) for the Script panel. So this problem will probably be gone then.

Sebastian

On Friday, February 8, 2013 9:08:32 AM UTC+1, Jim Michaels wrote:
>
> I am sure I said to please try to reproduce on a 32-bit XP box. I am sure 
> your nice fast 64-bit environment works wonderfully. on  my slow 32-bit 
> box, things don't work well.
> this is what I am having trouble on. I will give it a go on my 32-bit 8 
> box now that I can upload and try again. I am having similar problems on 
> everything I try to debug. I am pulling  hair out trying to fix bugs with 
> fb.
>
> one of the problems is when it gets to a return statement, instead of 
> putting the program pointer there, it skips over it and jumps somewhere 
> else. PLEASE try on a 32-bit xp box.
>
> On Tuesday, February 5, 2013 2:43:38 PM UTC-8, Sebastian Zartner wrote:
>>
>> I tried to reproduce your steps on FF 18.0.1 + FB 1.11.1 on Win8 and I 
>> still can't reproduce your issue.
>>
>> 6.go to function NamedTimeStringToDTime and put breakpoints on every 
>>> instance of GetIntegerKeywordPair() and StringDateTimeToDTime(). 174, 978, 
>>> 1850,1851,1882,1883, 1937,1945,1949,1956,1958,1967,1975,1979,1989,1997, 
>>> 2012,2020,2024,2043, 
>>
>> I assume these numbers should be the line numbers of the calls to 
>> GetIntegerKeywordPair() and StringDateTimeToDTime(). Though the only 
>> calls to these functions are in line 1920, 1940, 1970, 1992 and 2015.
>>
>> Anyway, I assume your problem doesn't lie in the slowness of your PC but 
>> may be caused by problems related to your graphics card. So please turn off 
>> hardware acceleration by unchecking *Tools > Options > Advanced > 
>> General > Use hardware acceleration when available*. Does the problem go 
>> away? If not, please update your graphics card driver and try it again with 
>> and without that option being checked.
>>
>> Sebastian
>>
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
https://groups.google.com/forum/#!forum/firebug

--- 
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to