Conversation

Notices

  1. Also why is chrome split into like 15 instances on task manager? All of them added together is still nearly 600,000k.

    Monday, 25-Jun-12 17:08:13 UTC from web
    1. @ecmc becus google dunno how to code

      Monday, 25-Jun-12 17:08:59 UTC from web
      1. @redenchilada Would you happen to have any idea why my firefox randomly started using up to 800,000k memory when I wasn't doing anything different?

        Monday, 25-Jun-12 17:11:34 UTC from web
        1. @ecmc Dunno, mine only uses ~400,000k with multiple Youtube videos up and one playing. Maybe an addon has a memory leak...? I dunno.

          Monday, 25-Jun-12 17:12:54 UTC from web
        2. @ecmc Which addons do you use?

          Monday, 25-Jun-12 17:14:08 UTC from web
          1. @bitshift Excluding plugins, adblock plus, avast webrep, derpy.me link shortener, and greasemonkey. Well those are the "Extensions" anyway.

            Monday, 25-Jun-12 17:17:51 UTC from web
            1. @ecmc Avast is the biggest red flag there. As one bundled with an antivirus package, it's both the most probable one to have suddenly had a silent update, and the most probable one to be coded badly. My second guess would be a tie between ABP and Greasemonkey; GM itself is coded well enough, but some of the scripts run via it can be real hogs; whereas ABP has run into genuine memory leak bugs in Firefox before, so it's entirely feasible it might have done it again.

              Monday, 25-Jun-12 17:21:09 UTC from web
              1. @bitshift ok I'll try disabling the avast one as I don't find it useful anyway.

                Monday, 25-Jun-12 17:23:35 UTC from web
            2. @ecmc Yeah try disabling Web Rep. I disabled it when I updated my Firefox and it seems to freeze less.

              Monday, 25-Jun-12 17:23:11 UTC from web
              1. @redenchilada @bitshift Well, looking good so far! Memory usage is hovering steadily at 330,000-350,000k. THANK YOU EGGHEADS :D

                Monday, 25-Jun-12 17:30:37 UTC from web
    2. @ecmc Separate processes. And the numbers in there include all the memory each can access, _some of which_ is shared between all, so it's not quite that bad. But still, it's generally enough in practice that I can't quite understand how Chrome is touted as more lightweight than Firefox. (Faster, yes, largely because they have fewer things that are still allowed to lag the entire interface; the actual rendering times are close enough nowadays that it doesn't really make a difference to all but the most obsessive user.)

      Monday, 25-Jun-12 17:12:50 UTC from web