Comments on: Take Three: Enter Opera

By: firsttube.com » Blog Archive » Firefox: Like An Old Shoe

firsttube.com » Blog Archive » Firefox: Like An Old Shoe — Wed, 20 Aug 2008 17:34:23 +0000

[...] has let me down many times before, and the Mozilla Firefox developers have disappointed me. So I switched to Opera, and it’s made me very happy. I have really learned to love Speed Dial, and user javascript [...]

By: Adam S

Adam S — Fri, 02 Feb 2007 16:43:34 +0000

The backslash character appears okay in the preview, but disappeared from the last post. If it appears in this post, that is because it is escaped by a second backslash.

Yes, thanks it's a bug that I have been lazy about fixing. I'll take care of it this weekend for sure.

By: R. A. Hicks

R. A. Hicks — Fri, 02 Feb 2007 16:23:30 +0000

Well something is regular expression challenged. The backslash character “ appears okay in the preview, but disappeared from the last post. If it appears in this post, that is because it is escaped by a second backslash. Here goes nothing.

By: R. A. Hicks

R. A. Hicks — Fri, 02 Feb 2007 16:08:21 +0000

Oops, forgot to put my name on that last post. Duh.

BTW, is Small Axe injecting the “ character into the Subject: line before the `’` character? It’s rather annoying.

By: Anonymous

Anonymous — Fri, 02 Feb 2007 15:41:54 +0000

IMHO, you suffer from low expectations.

BTW, I have observed that when Camino gets sufficiently bloated to start crushing the rest of the system to death, it seems to have a large number of (possibly zombie) JVM threads. Certainly, the process owns many more threads than it does when it starts up. Also, when I sample the process (i.e. select View > Sample Process from the Activity Viewer application), most of the threads seem to be stalled (i.e. every frame in the thread’s stack has the same frequency count implying that thread has not executed during the sampling period) inside the JVM (or at least, I am assuming that is the case from the symbol names prefixed with “JVM”). It is possible that zombie threads with undead JVMs might be responsible for much of the memory leakage. Just a theory, but I have experienced other problems with the JVM plugin for Camino.

Do you observe similar behaviour with Camino? I’d like to gather enough information to file a bug report, but at the moment I don’t really have anything specific enough to report.

By: Adam S

Adam S — Thu, 01 Feb 2007 13:18:50 +0000

Camino exhibits memory leaks and if left open for a couple of weeks

A couple of... WEEKS? That's fine by me!

FF and Flock exhibits problems after several hours of use. A single, uninterupted Camino session works for me for weeks - regularly. Optimistic or not, that's pretty damned good!

By: R. A. Hicks

R. A. Hicks — Thu, 01 Feb 2007 10:26:09 +0000

In my experience Camino exhibits memory leaks and if left open for a couple of weeks will eat much of system memory. Once that happens, the browser will hang whenever the automatic garbage collector is invoked. Eventually the browser’s garbage collector will thrash the system since traversing the object graph requires constant memory paging. Since a garbage collector is used, the likely source of many of the memory leaks is the failure to nullify a pointer when the object to which the pointer points is no longer needed. There is something of a misconception that in systems with automatic garbage collection, objects do not need to be released; in reality, the way to release an unneeded object is to nullify the referencing pointer.