there's really not much anyone here can do to help besides pointing you at the mozilla release page and bugzilla unless you post some code.

having it inaccessible (private or offline) or too large to post is a poor excuse. if you can't debug something, you should always reduce it to a minimal test case. make a copy of the codebase and start removing parts of the code, testing each time. each time you remove a piece, if the error is still reproduced, leave that piece out. if it makes the error go away, put it back in and start taking out other pieces. the goal is to eliminate every possible variable until you wind up with a tiny piece of code by changing one or two lines you can either reproduce the error or not. then post that if it hasn't become obvious where the problem is (99% of the time it will).

i don't mean to be too rough but i'm constantly amazed at how few people seem to be able to grasp this basic strategy. there's no magic secret to debugging code; you just have to go through it systematically and painstakingly. debuggers and logging (print statements or otherwise) can help but nothing i've found works as well as reducing it to a minimal test case.

anders pearson

In reply to Re: OT: Mozilla .9.9 (Linux) by thraxil
in thread OT: Mozilla .9.9 (Linux) by Ryszard

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.