Recommended Posts

why? they have been there since firefox 3 you would think **** would be fixxed by now way to much ram is being used in every version of firefox

You do not understand something very simple,

You are not using a version that is meant for general use.

Firefox 4.0 is not yet complete,

1. Restart-less plugin support is not here yet.

2. New JS engine is not here yet.

3. New rendering engine is not here yet.

4. Interface is not yet in its final form either.

Be quiet, sit down, and wait.

By the time it's using ~1GB things are not pretty, 4GB's or not.

Mine never uses over 350 mb and I have to have to have like 30 tabs and/or multiple flash tabs for that to happen. It generally stays around 100-200 mb for me. something is wrong on your end. Firefox uses less memory than opera chrome and IE as multiple benchmarks have shown. Memory problems in firefox are down to: extensions, plugins, or a issues with your profile.

And this version is also a beta...

Mine never uses over 350 mb and I have to have to have like 30 tabs and/or multiple flash tabs for that to happen. It generally stays around 100-200 mb for me. something is wrong on your end. Firefox uses less memory than opera chrome and IE as multiple benchmarks have shown. Memory problems in firefox are down to: extensions, plugins, or a issues with your profile.

And this version is also a beta...

Many people don't realize that there is are multiple Chrome.exe processes and so you get comments like, "Chrome only uses 5MB RAM with 20 tabs open" ....

Also,

If anyone is wandering where their RAM is going, Direct2D does actively leak memory.

that looks GREAT!, can u tell me how u get remove the feedback button and how did you remove the word bookmarks from the boomark icons and got the little arrow for the drop down menu?

I have to remove the feedback after each restart manually :s I'm using firefox 4.0 beta 1. I dont understand the thing with the bookmark icon. I did nothing with it :D

Here are my stylish settings:

For the tabs and the little dropdown menu arrow(Thanks for somebody in this forum):

    #appmenu-button-container {
        position: fixed !important;
        top:1px !important;
        left:0px !important;
    }

    #main-window[sizemode=maximized] #appmenu-button-container {
        top: 8px !important;
    }

    #appmenu-button {
        padding: 1px 5px 1px 5px !important;
        height:19px !important;
        min-width: 10px !important;
        width: 39px !important;
        background-image: -moz-linear-gradient(rgba(255,224,159,0.8), rgba(255,224,109,0.5) 40%, rgba(255,224,109,0.2) 50%, rgba(255,255,255,0.05) 51%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.7) 29%, rgba(248, 233, 164, 0.4) 35%, rgba(248, 233, 164, 0) 50%) !important;
        -moz-box-shadow: 0 0 5px rgba(255,255,255,.5) inset, 0 0 1px rgba(255,250,240,0.8) inset, 0 0 1px rgba(255,250,240,0.8) inset, 0 0 1px rgba(255,250,240,0.8) inset, 0 0 1px rgba(255,250,240,0.5) !important;
    }

    #appmenu-button:hover:active, #appmenu-button[open] {
        background-image: -moz-linear-gradient(rgba(0,0,0,.3), rgba(0,0,0,.2) 10%, transparent 60%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;
        -moz-box-shadow: 0 0 4px rgba(0,0,0,.3) inset !important;
    }

    #appmenu-button .button-text {
        color: transparent !important;
        text-shadow: none !important;
        margin-left: -25px !important;
        margin-right: -33px !important;
        background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAADK0lEQVQ4jV2TTWxUZRSGn++7d+bey3SYMgMzdNLMTCu2VcE0CjG1qYqRSEhYKElTA66MooaNLozDwh8WjAs3JsSFSxeKRg0axSj+EApFYotAS0ctWmeEOpTS6fx0fu+9n4v+pPqsTk7yvuck57wCIGXIT4BUsu6OBbr2bO+p5J71OfWHxvzxMEuMA6eBLwu/nxxlDWLZQAGcDG09Ou/xDR3IXegE2F9zEMDg/rd59eky1z467575pfLdrrmLRw7dqJxjWXwgZUh1682gShlSra2Ha0qdK9nq63xDbXniLTUx8pz68Y1+9U5XuPrhwMZBACkEjwRDGgD7hoLE457V9c4GNF5u9XK1WGfw4B4efT1B594eHnvlHrNUku99/mRks9SkuL/jTk+jkrVxF6ps7/Ovmu0bChKXUEQnH9uCMrx8MNJK4sEIoZgVKN9sJqXHENFou+ZtVl18iaXp1UKEjbuf4dPj86hTC1y+eJuJM3/hojF5rUGhYNO9K8TiXG2nrhTrfa0SXQoqJUnLwB0A6J5JAGamcuQn05RmctiuzlhaYkmHSNxkMe/06PWaa2CD2SYZ/rZE8/tRZnIKgKOPv0vz/Y8RysGSLtWaIJKo0Lp+nnylQq1o69LwiHKpoEBAMKKxye/S1iYBOPzNi3zW9wOv7chQnJ2jUczzcHsW8vOUf72J1SIqugZX/sk2+/0bNLruNvl73GZbXOfeHSY+0+ZC5hacOI3d/jwxK8vB3jT1XIPrZ/Nowh3XbUcdnxpv3BcI6VY4ZtK+LYjdcBj7aZHMHw3gKknfU/Sv+40Xdt8mpNVZmFpg8mcNb2vwlEgZssXSGNaF6N055Mc0dBxHR5oa03kvc8Ua68QisXCTRMKgik56pMyfGau4ObapWwAcMeQDluQLS4rw1j6LSFRD1ySapjCkjeMIbMAMQSarmLhUr81NOwPJujsqVr4uZcheQ+MrBdFQi6Sz20sgKNAtwCOYvd4kc0OgqnYlN+v2J+vupdUwrXDMp3W4gpdcpfY6UiQce+k6piHYEJA1p6lOlBfU4UOLzvR/0vh/jvm0DuAuILrcmgHSa4Ur/AsXclHwqDchzQAAAABJRU5ErkJggg==") no-repeat 15px !important;
    }

    #appmenu-button dropmarker {
        margin: 0 2px 0 0 !important;
    }

    #navigator-toolbox[tabsontop="true"] #TabsToolbar {
        padding: 0px 112px 0 0px !important;
    }

    #main-window[sizemode=normal] #navigator-toolbox[tabsontop="true"] #TabsToolbar {
    padding-top: 7px !important;
    padding-right: 102px !important;
    padding-left: 43px !important;

    }

    #main-window[sizemode=fullscreen] #navigator-toolbox[tabsontop="true"] #TabsToolbar {
    padding-right: 102px !important;
    padding-left:40px !important;
    }

The full screen settings ind the end are somehow not working :(

Transparent finder and buttons bacground:

/*True transparency in FF 4.01b, with orange FF theme highlights by Elian152, any code used form other sources has been credited above the code section*/


/*makes the Stumbleupon toolbar transparent*/
toolbar.chromeclass-toolbar#stumbleupon {border: none !important; background: none !important; text-shadow: #fff 0px 0px 10px, #fff 1px 1px 10px, #fff 1px 1px 3px !important;}
/*makes navigation and bookmarks toolbar  transparent when tabs are above*/
#nav-bar, #PersonalToolbar {border: none !important;     background: transparent !important; text-shadow: #fff 0px 0px 10px, #fff 1px 1px 10px, #fff 1px 1px 3px !important;}



/*Hides splitter bar that appears with stumbleupon after first restart*/
splitter.toolbar-splitter {display: none;}



/*Hides bookmarks button, bug scheduled to be fixed in later releases*/
#bookmarks-menu-button {} 

Transparent statusbar(the whole thing including search and download statusbar):

#browser-bottombox, statusbarpanel, #status-bar, #downbarHolder, .findbar-container
{ -moz-appearance: none !important;
  border: transparent !important;
  border-bottom: 0px !important;
  background: transparent !important;
  text-shadow: 0 0 1em white, 0 0 1ex white; }
.findbar-textbox.findbar-find-fast:not(:hover)
{ opacity:0.7!important; }

I have to remove the feedback after each restart manually :s I'm using firefox 4.0 beta 1. I dont understand the thing with the bookmark icon. I did nothing with it :D

Here are my stylish settings:

For the tabs and the little dropdown menu arrow(Thanks for somebody in this forum):

 #appmenu-button-container {
 position: fixed !important;
 top:1px !important;
 left:0px !important;
 }

 #main-window[sizemode=maximized] #appmenu-button-container {
 top: 8px !important;
 }

 #appmenu-button {
 padding: 1px 5px 1px 5px !important;
 height:19px !important;
 min-width: 10px !important;
 width: 39px !important;
 background-image: -moz-linear-gradient(rgba(255,224,159,0.8), rgba(255,224,109,0.5) 40%, rgba(255,224,109,0.2) 50%, rgba(255,255,255,0.05) 51%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.7) 29%, rgba(248, 233, 164, 0.4) 35%, rgba(248, 233, 164, 0) 50%) !important;
 -moz-box-shadow: 0 0 5px rgba(255,255,255,.5) inset, 0 0 1px rgba(255,250,240,0.8) inset, 0 0 1px rgba(255,250,240,0.8) inset, 0 0 1px rgba(255,250,240,0.8) inset, 0 0 1px rgba(255,250,240,0.5) !important;
 }

 #appmenu-button:hover:active, #appmenu-button[open] {
 background-image: -moz-linear-gradient(rgba(0,0,0,.3), rgba(0,0,0,.2) 10%, transparent 60%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;
 -moz-box-shadow: 0 0 4px rgba(0,0,0,.3) inset !important;
 }

 #appmenu-button .button-text {
 color: transparent !important;
 text-shadow: none !important;
 margin-left: -25px !important;
 margin-right: -33px !important;
 background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAADK0lEQVQ4jV2TTWxUZRSGn++7d+bey3SYMgMzdNLMTCu2VcE0CjG1qYqRSEhYKElTA66MooaNLozDwh8WjAs3JsSFSxeKRg0axSj+EApFYotAS0ctWmeEOpTS6fx0fu+9n4v+pPqsTk7yvuck57wCIGXIT4BUsu6OBbr2bO+p5J71OfWHxvzxMEuMA6eBLwu/nxxlDWLZQAGcDG09Ou/xDR3IXegE2F9zEMDg/rd59eky1z467575pfLdrrmLRw7dqJxjWXwgZUh1682gShlSra2Ha0qdK9nq63xDbXniLTUx8pz68Y1+9U5XuPrhwMZBACkEjwRDGgD7hoLE457V9c4GNF5u9XK1WGfw4B4efT1B594eHnvlHrNUku99/mRks9SkuL/jTk+jkrVxF6ps7/Ovmu0bChKXUEQnH9uCMrx8MNJK4sEIoZgVKN9sJqXHENFou+ZtVl18iaXp1UKEjbuf4dPj86hTC1y+eJuJM3/hojF5rUGhYNO9K8TiXG2nrhTrfa0SXQoqJUnLwB0A6J5JAGamcuQn05RmctiuzlhaYkmHSNxkMe/06PWaa2CD2SYZ/rZE8/tRZnIKgKOPv0vz/Y8RysGSLtWaIJKo0Lp+nnylQq1o69LwiHKpoEBAMKKxye/S1iYBOPzNi3zW9wOv7chQnJ2jUczzcHsW8vOUf72J1SIqugZX/sk2+/0bNLruNvl73GZbXOfeHSY+0+ZC5hacOI3d/jwxK8vB3jT1XIPrZ/Nowh3XbUcdnxpv3BcI6VY4ZtK+LYjdcBj7aZHMHw3gKknfU/Sv+40Xdt8mpNVZmFpg8mcNb2vwlEgZssXSGNaF6N055Mc0dBxHR5oa03kvc8Ua68QisXCTRMKgik56pMyfGau4ObapWwAcMeQDluQLS4rw1j6LSFRD1ySapjCkjeMIbMAMQSarmLhUr81NOwPJujsqVr4uZcheQ+MrBdFQi6Sz20sgKNAtwCOYvd4kc0OgqnYlN+v2J+vupdUwrXDMp3W4gpdcpfY6UiQce+k6piHYEJA1p6lOlBfU4UOLzvR/0vh/jvm0DuAuILrcmgHSa4Ur/AsXclHwqDchzQAAAABJRU5ErkJggg==") no-repeat 15px !important;
 }

 #appmenu-button dropmarker {
 margin: 0 2px 0 0 !important;
 }

 #navigator-toolbox[tabsontop="true"] #TabsToolbar {
 padding: 0px 112px 0 0px !important;
 }

 #main-window[sizemode=normal] #navigator-toolbox[tabsontop="true"] #TabsToolbar {
 padding-top: 7px !important;
 padding-right: 102px !important;
 padding-left: 43px !important;

 }

 #main-window[sizemode=fullscreen] #navigator-toolbox[tabsontop="true"] #TabsToolbar {
 padding-right: 102px !important;
 padding-left:40px !important;
 }

The full screen settings ind the end are somehow not working :(

Transparent finder and buttons bacground:

/*True transparency in FF 4.01b, with orange FF theme highlights by Elian152, any code used form other sources has been credited above the code section*/


/*makes the Stumbleupon toolbar transparent*/
toolbar.chromeclass-toolbar#stumbleupon {border: none !important; background: none !important; text-shadow: #fff 0px 0px 10px, #fff 1px 1px 10px, #fff 1px 1px 3px !important;}
/*makes navigation and bookmarks toolbar transparent when tabs are above*/
#nav-bar, #PersonalToolbar {border: none !important; background: transparent !important; text-shadow: #fff 0px 0px 10px, #fff 1px 1px 10px, #fff 1px 1px 3px !important;}



/*Hides splitter bar that appears with stumbleupon after first restart*/
splitter.toolbar-splitter {display: none;}



/*Hides bookmarks button, bug scheduled to be fixed in later releases*/
#bookmarks-menu-button {} 

Transparent statusbar(the whole thing including search and download statusbar):

#browser-bottombox, statusbarpanel, #status-bar, #downbarHolder, .findbar-container
{ -moz-appearance: none !important;
 border: transparent !important;
 border-bottom: 0px !important;
 background: transparent !important;
 text-shadow: 0 0 1em white, 0 0 1ex white; }
.findbar-textbox.findbar-find-fast:not(:hover)
{ opacity:0.7!important; }

A big thkz!!!I just realize whats going on with the bookmark button, I have the bookmar toolbar enable

Gosh! So many features in one browser!

And folks accuse *IE* of being bloated...

Here is something I find absolutely hi-larious (though I have IE as my default in Windows, I do have Firefox 4 beta 1 installed there); the same folks that have complained about IE code-bloat and feature-bloat load up the Fox with add-ons/extensions/plug-ins; do you really think that just because a feature is an add-on/extension/plug-in it doesn't weigh down the browser? If anything, a feature that is an add-on/extension/plug-in (as opposed to designed/built in) weighs it down more, not less. Firefox has a cottage-industry of add-ons/extensions/plug-ins; I will give it that. (Most of these are unique.) However, it is precisely because of that cottage industry that Firefox defaulters have, if anything, far less reason to gripe about code-bloat or feature-bloat then IE-defaulters.

You are wrong for using ANY version of STYLISH! userChrome.css is the file to hack. I took all of the "stylish" code and corrected the numerous errors and created a chrome that does this and works flawlessly. I have a newer build of OMNIBAR installed from a link at the developers web site to finish the look. The chrome is yours to enjoy as much as I do.userChrome.css

Of course we know you can use userChrome.css. Stylish is awesome because it lets you change things on the fly, separate different elements and toggle them on and off, all without restarting your browser.

Stylish has to go through two steps EVERYTIME you launch the browser! You have to go and unselect your style preference and then reselect for it to work. Who in their right mind thinks that a viable choice? Stylish is not compatible with 4.0. The older version of stylish that others like you are using does not load your "style" automatically. The developer, whose forum I spent hours combing through, will not update it until firefox is in RC1or2.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Absolutely NOBODY has suggested such a conclusion. I am affirming the sober reality check that AV2's overall market adoption will take longer than AV1's adoption rate -- which, by the way, is the whole point of the article! While PCI-SIG is productive (on paper), other WGs have created all sorts of confusing progress plans that consumers have tuned-out of their improvements... HTML/W3C, USB, HDMI, BT, WIFI (ieee802.11) as a few other groups where spec naming conventions, split progress paths, overlapping ambitions... I'm not critiquing the AV specs group; I'm simply affirming that adoption for AV2 faces headwinds beyond the macroeconomics of it all.
    • Segra 1.5.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.5.2 changelog: Settings: Added an Airplane Mode that hides account, login, and upload features. Storage: Added a button to migrate videos into the recording path after changing it. Import: Added auto-scroll and a highlight pulse to videos right after importing. Recording: Added graceful handling of low disk space and output failures, finalizing files safely with clear errors. Recording: Added a guard blocking recording when any drive exceeds 99% full. OBS: Removed the download timeout to support users with slow internet. Clips: Fixed an error modal incorrectly appearing when clip creation was cancelled. Settings: Fixed the content folder path not refreshing in the UI after changes. Updates: Improved error handling for multiple simultaneous update checks. Stability: Fixed a WebSocket reconnect loop that ran while the window was backgrounded. Dependencies: Updated project dependencies. Maintenance: Removed dead code, reduced duplication, and fixed several latent bugs. Download: Segra 1.5.2 | 73.1 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • No thanks! WebView trash is unacceptable. I only use software that's native.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      465
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      70
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!