Comments on: Firefox developer preview brings out of process plugins

By: emusings

emusings — Fri, 09 Apr 2010 08:21:02 +0000

I’m running FFox 3.7a4 pre. I too had 3 mozilla-runtime processes actively leaking memory.

But it’s not the Shockwave plugin.

It’s Macromedia Shockwave for Director Netscape v10.1.1.16 along with RealPlayer Version Plug-in 6.0.12.1348 and RealPlayer G2 LiveConnect-enabled Plug-in (32-bit) 6.0.11.2240.

I disabled these 3 but let Shockwave alone and my memory usage is back under control.

By: Aldo "xoen" Giambelluca

Aldo "xoen" Giambelluca — Thu, 01 Apr 2010 14:02:08 +0000

I agree, better if the process name is something like mozilla-plugin-PLUGINNAME.exe or firefox-plugin-PLUGINNAME.exe

By: Aldo "xoen" Giambelluca

Aldo "xoen" Giambelluca — Thu, 01 Apr 2010 14:00:26 +0000

I vote for mozilla-plugin-PLUGINNAME.exe :)

By: El Firefox 3.7 alpha 2 té un nou tema al Windows « mozilla.cat

El Firefox 3.7 alpha 2 té un nou tema al Windows « mozilla.cat — Mon, 22 Mar 2010 09:58:35 +0000

[...] un primer moment no me n’havia adonat, però llegint un apunt al bloc Mozilla Links ho he vist i he volgut anar-ho a comprovar: el Firefox 3.7 alpha 2 té un nou aspecte als sistemes [...]

By: JustZisGuy

JustZisGuy — Mon, 08 Mar 2010 19:39:06 +0000

Nice, that crashed plug in graphic is reminiscent of the “sad mac” one would get on old macs when something crashed.

I’m still curious what kind of user testing, if any, is going in to the Firefox 4 user interface changes.

Oh, and there’s nothing wrong with good old Windows 95: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18

By: jrk

jrk — Sat, 06 Mar 2010 00:16:32 +0000

Ken, by toolbar buttons I mean toolbar buttons. :-) Reload, home etc. No native app in Windows has borders around button icons (when you are not hovering over it).

unfortunatelly, Firefox 4 mockups show Mozilla following Opera’s lead in developing exotic interfaces.

By: Ken Saunders

Ken Saunders — Fri, 05 Mar 2010 04:46:39 +0000

Thanks Anonymous Cow.

jrk
“Toolbar buttons with borders???”
What do you mean borders? The title bar close, minimize, etc buttons?

By: Ferdinand

Ferdinand — Thu, 04 Mar 2010 21:22:45 +0000

[q]Also the bugs that prevented correct tab preview from Windows 7 task bar on Firefox 3.6, seem to be ironed and it works perfectly now.[/q]
They seem to be ironed out but they are not. The preview works but the right click menu does not work. This means that you can’t maximize, move etc.

By: Erik

Erik — Thu, 04 Mar 2010 21:22:14 +0000

Calling the process mozilla-runtime.exe doesn’t seem that intuitive. What about the more descriptive mozilla-plugin.exe?

By: Aubrey

Aubrey — Thu, 04 Mar 2010 21:13:29 +0000

if you called it flash-runtime.exe then stupid FF users would stop blaming memory leaks on you, FF!

By: Anonymous Cow

Anonymous Cow — Thu, 04 Mar 2010 21:06:31 +0000

The extra memory is probably not much more at all — typically task managers present memory in an information poor way. That is, 60k might be what that process is taking up, if it were the only process running and if all the files it has open were read and forced into memory (as well as any other mapped memory). Anyway, the point is, adding another mozilla-runtime isn’t nearly as much overhead as you might guess from looking at task manager. And even having one isn’t much, since it probably shares a large footprint with the firefox process.

By: jrk

jrk — Thu, 04 Mar 2010 20:24:42 +0000

Great but… Toolbar buttons with borders??? It seems Mozilla designers like Windows 95 style.

By: Ken Saunders

Ken Saunders — Thu, 04 Mar 2010 20:03:06 +0000

Hey is that additional memory that is used (the 60K+ instance), or would that just typically have been added to the total firefox.exe uses?

Have you dived into (the early stages of) DirectWrite and Direct2D yet?
http://weblogs.mozillazine.org/asa/archives/2010/02/direct2d_landed_in_f.html