[opensuse] Mozilla - Acrobat plugin using Lots of memory High System Load?
Listmates, I noticed that my laptop was really warm and the fan was working very very hard. Checking top, the culprit was: 10059 david 20 0 1767m 1.1g 4016 R 52 60.7 21:47.38 ld-linux.so.2 Evidently this has something to do with Adobe Acrobat 8 which had been called by Mozilla firefox during browsing. This is the first time this has happened. What's going on? Anyone else caught by the on 11.0 x86_64? What in the heck is this thing doing trying to reserve 1.1g of memory? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 05 November 2008 19:11, David C. Rankin wrote:
Listmates,
I noticed that my laptop was really warm and the fan was working very very hard. Checking top, the culprit was:
10059 david 20 0 1767m 1.1g 4016 R 52 60.7 21:47.38 ld-linux.so.2
Evidently this has something to do with Adobe Acrobat 8 which had been called by Mozilla firefox during browsing. This is the first time this has happened. What's going on? Anyone else caught by the on 11.0 x86_64?
I've seen such symptoms on a 32-bit system. It's possible there's some sequence of opening PDFs in the stand-alone app and in the browser that sets you up for this or some particular property of the documents viewed, but it may just be a random (-ish) bug. I do know that I've seen this even it appears that Firefox has shut down.
What in the heck is this thing doing trying to reserve 1.1g of memory?
Why do people hoard things??
-- David C. Rankin
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz schrieb:
On Wednesday 05 November 2008 19:11, David C. Rankin wrote:
Listmates,
I noticed that my laptop was really warm and the fan was working very very hard. Checking top, the culprit was:
10059 david 20 0 1767m 1.1g 4016 R 52 60.7 21:47.38 ld-linux.so.2
Evidently this has something to do with Adobe Acrobat 8 which had been called by Mozilla firefox during browsing. This is the first time this has happened. What's going on? Anyone else caught by the on 11.0 x86_64?
I've seen such symptoms on a 32-bit system. It's possible there's some sequence of opening PDFs in the stand-alone app and in the browser that sets you up for this or some particular property of the documents viewed, but it may just be a random (-ish) bug. I do know that I've seen this even it appears that Firefox has shut down.
Probably related to that: https://bugzilla.novell.com/show_bug.cgi?id=363381 ? Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2008-11-06 at 10:32 +0100, Wolfgang Rosenauer wrote:
Probably related to that: https://bugzilla.novell.com/show_bug.cgi?id=363381 ?
FYI, in 32 bits, I have known "for years" that when you open a PDF in firefox/mozilla, acrobat stays loaded at least till firefox exits, or acrobat is killed manually - closing the tab displaying the file is not enough. And it uses a lot of memory, so killing it manually is something to consider. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkS2ywACgkQtTMYHG2NR9XkkwCgiMWjWmRjsUM/nrgBnpRdhJer t+MAn00zdF/XP3OQ3YaQq3m1Fw094VZx =46bP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Thursday, 2008-11-06 at 10:32 +0100, Wolfgang Rosenauer wrote:
Probably related to that: https://bugzilla.novell.com/show_bug.cgi?id=363381 ?
FYI, in 32 bits, I have known "for years" that when you open a PDF in firefox/mozilla, acrobat stays loaded at least till firefox exits, or acrobat is killed manually - closing the tab displaying the file is not enough. And it uses a lot of memory, so killing it manually is something to consider.
This is well-known to me also. As well as memory acroread sometimes takes CPU. It's very annoying to have to exit firefox every day or so. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2008-11-05T21:11:19, "David C. Rankin"
Listmates,
I noticed that my laptop was really warm and the fan was working very very hard. Checking top, the culprit was:
10059 david 20 0 1767m 1.1g 4016 R 52 60.7 21:47.38 ld-linux.so.2
Evidently this has something to do with Adobe Acrobat 8 which had been called by Mozilla firefox during browsing. This is the first time this has happened. What's going on? Anyone else caught by the on 11.0 x86_64?
What in the heck is this thing doing trying to reserve 1.1g of memory?
It's called a bloody bug, of the annoying variety. Acrobat and sometimes Flash do happen to get into such states. Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 06 November 2008 04:15, Dave Howorth wrote:
Carlos E. R. wrote:
On Thursday, 2008-11-06 at 10:32 +0100, Wolfgang Rosenauer wrote:
Probably related to that: https://bugzilla.novell.com/show_bug.cgi?id=363381 ?
FYI, in 32 bits, I have known "for years" that when you open a PDF in firefox/mozilla, acrobat stays loaded at least till firefox exits, or acrobat is killed manually - closing the tab displaying the file is not enough. And it uses a lot of memory, so killing it manually is something to consider.
This is well-known to me also. As well as memory acroread sometimes takes CPU. It's very annoying to have to exit firefox every day or so.
Actually, I've long given up trying to keep Firefox running day-to-day and now shut it down every night and restart it the next morning. I'm still running 2.0.x (on SuSE Linux 10.0) and I believe this version is known to have memory leaks. I keep many windows and very many tabs open and use Tab Mix Plus. Tab Mix Plus seems to have a certain probability of triggering a deadlock during shutdown (requiring me to kill Firefox) when I'm confirming the "You are about to close N tabs" alerts (actually, it's a pure hunch that Tab Mix Plus is involved in this, since I've been using it so long I don't really have a valid control case with which to compare the behavior I see). I've found that if I watch the CPU meter in the System Monitor applet and wait for the CPU usage to die down before clicking the OK, I can avoid the deadlock. Also, I've noticed that on my openSUSE 10.3 box, Firefox will spontaneously die on me, always when I'm not actively using it! I'll just look up at some point and it will be gone. This system is a secondary one and I never have so many windows and tabs open (and the system has twice as much memory, 4 GB, as the 10.0 system). Anyway, Firefox at least as of 2.0.0.10 and 2.0.0.17, is not what I'd call "bug-free" or even entirely reliable or stable...
Cheers, Dave
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R.
-
Dave Howorth
-
David C. Rankin
-
Lars Marowsky-Bree
-
Randall R Schulz
-
Wolfgang Rosenauer