I have been seeing some intermittency in Firefox and am trying to suss out the issue. Some times a page loads fine, some times it stalls. It's completely erratic, making it hard to diagnose. Anyone want to jump in and give me a hand?
How could I help you?
Regards,
--
Pablo Olmos de Aguilera Corradini - @PaBLoX
http://www.glatelier.org/
http://www.mozillachile.org/
http://friendfeed.com/pablox/
http://www.linkedin.com/in/pablooda/
Linux User: #456971 - http://counter.li.org/
--
You received this message because you are subscribed to the Google Groups "eCSStender Mailing List" group.
To post to this group, send email to ecsst...@googlegroups.com.
To unsubscribe from this group, send email to ecsstender+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ecsstender?hl=en.
> On 2 December 2010 17:10, Aaron Gustafson <aa...@easy-designs.net> wrote:
>>
>> On 2 Dec 2010, at 2:01 PM, Pablo Olmos de Aguilera Corradini wrote:
>>
>>> When I navigate (or try to) through the website, its get "stuck", and
>>> drops the following message:
>>>
>>> A script on this page may be busy, or it may have stopped responding.
>>> You can stop the script now, open the script in the debugger, or let
>>> the script continue.
>>>
>>> Script: http://ecsstender.org/j/main.js:20
>>>
>>> If I put continue, it happens 3 or 4 times before loading (in the
>>> meantime I can see that the border-radius isn't working; just see
>>> squares), after that I see the -moz-border-radius.
>>>
>>> I saw a similar message, but I couldn't reply it to the group.
>>
>>
>> I have been seeing some intermittency in Firefox and am trying to suss out the issue. Some times a page loads fine, some times it stalls. It's completely erratic, making it hard to diagnose. Anyone want to jump in and give me a hand?
>
> How could I help you?
Apologies for the incredible delay getting back to you... the end of the year plus the holidays meant I didn't have a whole lot of free time.
If you fork the project and work with the source file (in /src), you can start logging to the console throughout the primary execution route eCSStender takes. The log in Firebug should give you a sense of where the stall is occurring. Running the included test suite (in /test) is your best bet as the extensions it uses are not very complex and are only meant to test the system.
Let me know if you have questions.