A place to log my programming solutions.
Programming
Geek/Humor
Resources
Personal
About NVNCBL

Tagged :: firefox

9
Mar 10

Google Chrome – Goodbye Firefox

Posted in Personal | Trackback | No Comments

I’ve become fed up with Firefox’s memory leak problem.  Most of us have seen the browser occupying upwards of 1GB, but even today’s offense of just 461MB (5 tabs open) was the final nail in the coffin.  Taking recommendations from co-workers and friends, I installed Google Chrome.  It’s lightning fast.  The transition process was smooth and painless — bookmarks, browsing history, and saved passwords were all migrated.  I’m excited to see how the browser integrates with Google’s online services (e.g. bookmark sync)

firefox-memory-leak

Don’t get me wrong, I love Firefox and once touted it as the best thing to happen to the Internet since broadband came out.  Too bad the rest of my system slows to the point where I’m experiencing issues with basic keyboard and mouse input.  I know I’ll have to come back to Firefox every now and then because of the developer toolbar, but it’s no longer my default browser.  Did I mention that Chrome is fast?

12
Oct 09

Script Double Run / Double Execute Phenomenon

Posted in Programming | Trackback | No Comments

I had a problem with your PHP code running or executing seemingly twice.  To debug this phenomenon, I put some write-to-file code at the beginning of the script.  Surprisingly, whenever I loaded my script in the browser, the file would be written to twice despite my one page load.

The problem was that The page I was developing had an <img> in it with the “src” attribute set blank.  When the document was fully loaded, javascript was in place to dynamically assign the “src”.  This worked perfectly fine in the pre-server-side-logic stage of development so it was an easy decision to begin debugging server-side logic.

The double execute happens when Firefox sees <img src=”" />.  Not knowing what source to assign, it sends a request (the second request) to the current path (again) for the image.  Therein lies the problem.  It’s interesting to note that Firefox is not to blame, as it’s following HTML specification.

About NVNCBL and Myself

Contact Me