IE memory usage with code project......
-
I'm not the biggest fan of Firefox either. It's only my first choice due to firebug. My biggest problem with IE 8 is that can be really sluggish when it comes to rendering tabs. The memory increase happens pretty rapidly though.... Flame-war averted??
JimBob SquarePants ******************************************************************* "He took everything personally, including our royalties!" David St.Hubbins, Spinal Tap about Ian Faith, their ex-manager *******************************************************************
I have nothing against Firefox. Personally, I don't like it, but that's more the user interface than its HTML rendering abilities. What always annoys me is the very unhelpful "X sucks" in response to a "I am having a problem with X" posts.
-
Ah, the old IE's rubbish line. He should probably switch to Firefox, then. Except: "Firefox sometimes uses more memory (RAM) than it should." "Firefox's memory usage may increase if it's left open for long periods of time. A workaround for this is to periodically restart Firefox." Not my opinion, you understand, but Mozilla's[^]
Electron Shepherd wrote:
Ah, the old IE's rubbish line. He should probably switch to Firefox Google Chrome, then
FTFY! I did - and I haven't been back...
You should never use standby on an elephant. It always crashes when you lift the ears. - Mark Wallace C/C++ (I dont see a huge difference between them, and the 'benefits' of C++ are questionable, who needs inheritance when you have copy and paste) - fat_boy
-
Electron Shepherd wrote:
Ah, the old IE's rubbish line. He should probably switch to Firefox Google Chrome, then
FTFY! I did - and I haven't been back...
You should never use standby on an elephant. It always crashes when you lift the ears. - Mark Wallace C/C++ (I dont see a huge difference between them, and the 'benefits' of C++ are questionable, who needs inheritance when you have copy and paste) - fat_boy
-
Without having looked at the source of CP - this is a very common problem due to IE's garbage garbage collector (no typo, the double garbage was intended) which becomes very apparent if the site is using JS closures, a very typical scenario if XMLHTTP is in action. FF is a little better at handling this, but has other problems, and webkit browers even a bit better (in general). Do not get me wrong, I'm not rating browsers here, I'm simply pointing out a fact on garbage collectors. //L
Hmmm....Never thought of that. It does seem to be specific to cp.
JimBob SquarePants ******************************************************************* "He took everything personally, including our royalties!" David St.Hubbins, Spinal Tap about Ian Faith, their ex-manager *******************************************************************
-
I have nothing against Firefox. Personally, I don't like it, but that's more the user interface than its HTML rendering abilities. What always annoys me is the very unhelpful "X sucks" in response to a "I am having a problem with X" posts.
It does seem to run this best though Browser Pong[^]
JimBob SquarePants ******************************************************************* "He took everything personally, including our royalties!" David St.Hubbins, Spinal Tap about Ian Faith, their ex-manager *******************************************************************
-
It does seem to run this best though Browser Pong[^]
JimBob SquarePants ******************************************************************* "He took everything personally, including our royalties!" David St.Hubbins, Spinal Tap about Ian Faith, their ex-manager *******************************************************************
I closed the window that launched browser pong, and spent about 30 seconds chasing the "ball" browser around the screen trying to close it before finally closing it through task manager.
-
I closed the window that launched browser pong, and spent about 30 seconds chasing the "ball" browser around the screen trying to close it before finally closing it through task manager.
Eeek! I didn't do that. Just got thrashed instead.
JimBob SquarePants ******************************************************************* "He took everything personally, including our royalties!" David St.Hubbins, Spinal Tap about Ian Faith, their ex-manager *******************************************************************
-
Hmmm....Never thought of that. It does seem to be specific to cp.
JimBob SquarePants ******************************************************************* "He took everything personally, including our royalties!" David St.Hubbins, Spinal Tap about Ian Faith, their ex-manager *******************************************************************
It won't roar its ugly head unless you keep pages open. The concept is that a prepetitive/interval/looped task that utilises closures bleed memory. This is because IE's (in particular) garbage collector doesnt undestand that the objects used are ready for collection, because of a circular referense between them. As such the garbage collector thinks object A is needed because it points to object B and vice versa. I'm not saying this is the case with CP, but with the behaviour you described I would not be surprised if it is. Cheers, //L
-
It won't roar its ugly head unless you keep pages open. The concept is that a prepetitive/interval/looped task that utilises closures bleed memory. This is because IE's (in particular) garbage collector doesnt undestand that the objects used are ready for collection, because of a circular referense between them. As such the garbage collector thinks object A is needed because it points to object B and vice versa. I'm not saying this is the case with CP, but with the behaviour you described I would not be surprised if it is. Cheers, //L
Cool... Learn something new every day.. Cheers!
JimBob SquarePants ******************************************************************* "He took everything personally, including our royalties!" David St.Hubbins, Spinal Tap about Ian Faith, their ex-manager *******************************************************************
-
Without having looked at the source of CP - this is a very common problem due to IE's garbage garbage collector (no typo, the double garbage was intended) which becomes very apparent if the site is using JS closures, a very typical scenario if XMLHTTP is in action. FF is a little better at handling this, but has other problems, and webkit browers even a bit better (in general). Do not get me wrong, I'm not rating browsers here, I'm simply pointing out a fact on garbage collectors. //L
hmmmm I wonder if this could have anything to do with the problems I was having last night at daily motion. In both FF and Opera I opened about a dozen videos at once in different tabs and did something else while the whole lot was loading only to have the browsers crash on me after a few minutes. I didn't think to look at what they were doing RE memory usage or anything; but cutting the number shown at a time was sufficient to prevent a crash...
3x12=36 2x12=24 1x12=12 0x12=18
-
It won't roar its ugly head unless you keep pages open. The concept is that a prepetitive/interval/looped task that utilises closures bleed memory. This is because IE's (in particular) garbage collector doesnt undestand that the objects used are ready for collection, because of a circular referense between them. As such the garbage collector thinks object A is needed because it points to object B and vice versa. I'm not saying this is the case with CP, but with the behaviour you described I would not be surprised if it is. Cheers, //L
Obligatory AI Koan[^] One day a student came to Moon and said: “I understand how to make a better garbage collector. We must keep a reference count of the pointers to each cons.” Moon patiently told the student the following story: “One day a student came to Moon and said: ‘I understand how to make a better garbage collector...
3x12=36 2x12=24 1x12=12 0x12=18
