Hi Paul,

The reality with all of these things will come down to "Who cares the most?"  Christopher makes the completely correct point "It's a problem between something in FF and (DNN)6" - I Inserted DNN for clarity.

I know from experience that it is extremely hard to track down this kind of bug.  One of my own (DNN) sites can occasionally crash IE8.  I cannot identify any specific HTML that causes the crash because I cannot reliably see it crash.  As far as I can tell it only affects a specific combination of IE8 and MSHTML.DLL.  I have no way of knowing how common that combination is.  I run IE8 on Win7 64bit myself.  It *NEVER* crashes on my main machine.  Personally, I only ever see the crash in a VM running Windows XP 32bit.  I cannot tell if this is a problem that affects lots of people coming to my site unless they choose to email and tell me.

If *you* care then the best thing you can possibly do is isolate an HTML file that reliably crashes FF6.  If it's valid HTML then send it to Mozilla, if it's not valid HTML then we'd need to look at DNN to see what makes it create invalid HTML.  If it crashes for you, but not someone else then we need to look at what's different between your machine and his.

At the moment we have a situation where clearly *somthing* does not work for you and some others and that same *somthing* works fine for others.  Without better targetted evidence, you are not likely to get a solution.

If this really does *realiably* crash FF6 then the best thing you can possibly do is post the simplest HTML file that shows it.  Especially as that will allow a lot of people to chip in with "works/does not work for me!"

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

This is still an issue for me but I have narrowed it down - in my case anyway - to when I am using the CKeditor and I hit 'Source' in the menu. It then crashes FF (Not responding), computer locks up, then it will come back up and sometimes I can finish in Source without having to move the entire process over to Chrome.

The reason that switching browsers is not a solution is that clients are going to be working in FF, Chrome, whatever, and they need not see this issue.

Please DNN folks have a look.

thanks,

Will