On 11 April 2016 at 15:04, Carlos E. R. wrote:

I would suspect heat. Flash is very CPU intensive.

That's a good idea, thanx. I will put some heat monitor widget and monitor that. But if that is the case, is there some workaround? Like limiting the priority or setting different overheating strategy? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 12 Apr 2016 10:31:21 +0200 Stanislav Baiduzhyi wrote:

On 11 April 2016 at 15:04, Carlos E. R. wrote:

...

I would suspect heat. Flash is very CPU intensive.

That's a good idea, thanx. I will put some heat monitor widget and monitor that. But if that is the case, is there some workaround? Like limiting the priority or setting different overheating strategy?

If heat is the problem, it's probably already operating at or very near the upper margins. In my experience, thermal protection shutdowns are very serious; generally the last line of defense. When this happens, it means the current operating state / environment is not healthy for the electronics. As a start, I'd make sure that all the fans are working and the heat sinks and vents are completely clear of dust. From the looks of the mechanical design, I'd also make sure that the back side, where the ports and vents are, isn't pushed into a corner or up against a wall. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 12 Apr 2016 12:21:29 +0200 Daniel Bauer wrote:

Am 12.04.2016 um 10:59 schrieb Carl Hartung:

...

On Tue, 12 Apr 2016 10:31:21 +0200 Stanislav Baiduzhyi wrote:

...

On 11 April 2016 at 15:04, Carlos E. R. wrote:

...

I would suspect heat. Flash is very CPU intensive.

That's a good idea, thanx. I will put some heat monitor widget and monitor that. But if that is the case, is there some workaround? Like limiting the priority or setting different overheating strategy?

If heat is the problem, it's probably already operating at or very near the upper margins. In my experience, thermal protection shutdowns are very serious; generally the last line of defense. When this happens, it means the current operating state / environment is not healthy for the electronics. As a start, I'd make sure that all the fans are working and the heat sinks and vents are completely clear of dust. From the looks of the mechanical design, I'd also make sure that the back side, where the ports and vents are, isn't pushed into a corner or up against a wall.

I had this problem with my desktop pc. I had to remove the graphic card that was actually completely "glued" with dust (shocked to see what "air" I breathe in Barcelona...) and use the vacuum cleaner.

I now have gkrellm on the desktop to show me the temperatures...

The OP wrote that the system has a (lower frequency range / lower power consumption) 'U' series processor and it's running the (built-in) Intel graphics, not a separate GPU / display adapter. All things being equal, I find it a little surprising to see thermal shutdowns triggered on that kind of hardware. It's almost certainly a ventilation, cooling (or even a design) issue. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/04/16 21:29, John Andersen wrote:

I've seen Youtube choke my opensuse 13.2 to death progressively, the longer I watch something the more it degrades the image, tearing starts appearing the machine starts thrashing the drive. I'm convinced it is a memory leak, but haven't spent a great deal of time tracking it down.

I get that on my 13.1 install (nVidia driver). Being in France I'd started to suspect it was my French ISP deliberately throttling Google/YouTube, because that's a thing here in recent years. All part of an effort to force providers of big bandwidth applications and data to pay more. Very anti-net-neutrality. I know my machine is perfectly capable of full screen (1280x800) video, but frequently with YouTube in particular, it all falls apart after the initial few minutes. I have to keep pausing and restarting after a while to avoid lag, yet the progress bar indicates that it has already read well ahead. CPU temperatures on my laptop of late have sometimes reached the mid-90s. Alarming. Fan/heatsink cleaned out. Same 13.1 install for over two years. No obvious runaway processes most of the time. Don't know if software resource demands are just getting too much lately. gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-04-12 21:41, gumb wrote:

On 12/04/16 21:29, John Andersen wrote:

...

I've seen Youtube choke my opensuse 13.2 to death progressively, the longer I watch something the more it degrades the image, tearing starts appearing the machine starts thrashing the drive. I'm convinced it is a memory leak, but haven't spent a great deal of time tracking it down.

A memory leak should not crash the machine hard, and without traces in logs. The kernel should react and start killing things. It would not be a sudden crash.

I get that on my 13.1 install (nVidia driver). Being in France I'd started to suspect it was my French ISP deliberately throttling Google/YouTube, because that's a thing here in recent years. All part of an effort to force providers of big bandwidth applications and data to pay more. Very anti-net-neutrality.

I know my machine is perfectly capable of full screen (1280x800) video, but frequently with YouTube in particular, it all falls apart after the initial few minutes. I have to keep pausing and restarting after a while to avoid lag, yet the progress bar indicates that it has already read well ahead.

I prefer to use something to download the video, and watch it later with another player, like VLC, outside of the browser. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlcNeqIACgkQja8UbcUWM1w1OAD9HVdd5MPAKM/6Ppt7MGl3rEDz 7lxcLTTzSdudgz/+r+IA/0UpnHoAllsjZNTlbgqJv44TTxQvj1XCwTutspI3GE7C =NIgU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 13 April 2016 at 00:45, Carlos E. R. wrote:

A memory leak should not crash the machine hard, and without traces in logs. The kernel should react and start killing things. It would not be a sudden crash.

Definitely not RAM-related, have 16GB installed and system monitor shows around 15GB available.

I prefer to use something to download the video, and watch it later with another player, like VLC, outside of the browser.

Would be great, but some flash-based video players are splitting video into smaller chunks so I cannot download them until I will watch the entire length. Yesterday I reproduced the issue once again. Does not look like overheating, system is staying at 49C all the time, then I press pause, leave it for some time, it cools down to 47C, I unpause and BAM - it reboots again in milliseconds after the mouse button is up. I remember there was some change about the flash player, Chrome uses embedded version but Firefox should use system version, right? What changed there, it was provided previously but now have to install it from Adobe directly? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Op woensdag 13 april 2016 10:10:44 CEST schreef Stanislav Baiduzhyi:

On 13 April 2016 at 00:45, Carlos E. R. wrote:

...

A memory leak should not crash the machine hard, and without traces in logs. The kernel should react and start killing things. It would not be a sudden crash.

Definitely not RAM-related, have 16GB installed and system monitor shows around 15GB available.

...

I prefer to use something to download the video, and watch it later with another player, like VLC, outside of the browser.

Would be great, but some flash-based video players are splitting video into smaller chunks so I cannot download them until I will watch the entire length.

Yesterday I reproduced the issue once again. Does not look like overheating, system is staying at 49C all the time, then I press pause, leave it for some time, it cools down to 47C, I unpause and BAM - it reboots again in milliseconds after the mouse button is up.

I remember there was some change about the flash player, Chrome uses embedded version but Firefox should use system version, right? What changed there, it was provided previously but now have to install it from Adobe directly?

Packman has flash-player, the one from Adobe itself (often) has issues with signing. BTW: Nobody knows youtube-dl (available from Packman) ? Nobody uses HTML5 on Youtube? -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2016-04-13 10:10, Stanislav Baiduzhyi wrote:

I remember there was some change about the flash player, Chrome uses embedded version but Firefox should use system version, right? What changed there, it was provided previously but now have to install it from Adobe directly?

No, from packman. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2016-04-12 at 10:31 +0200, Stanislav Baiduzhyi wrote:

On 11 April 2016 at 15:04, Carlos E. R. wrote:

...

I would suspect heat. Flash is very CPU intensive.

That's a good idea, thanx. I will put some heat monitor widget and monitor that. But if that is the case, is there some workaround? Like limiting the priority or setting different overheating strategy?

There are two things. One, is that a computer should be able to disipate addequately the heat generated at full continuous load. But this does not always happen, typically because of problems (like dust), but also by design: the machine is is not designed for full continuous load on warm weather, worst case scenario, but sporadic, short bursts. And two, it is my opinion, often stated, that the operating system should monitor the temperature of the CPU and take measures if it overheats, to avoid crashing. What measures? Throttling. First step is to slow the clock. Second is to insert iddle instructions. You can limit a process: cpulimit (1) - limits the CPU usage of a process Searching for that one I just found this other: cer@Telcontar:~> apropos cpupower cpupower (1) - Shows and sets processor power related values cpupower-frequency-info (1) - (unknown subject) cpupower-frequency-set (1) - (unknown subject) cpupower-info (1) - Shows processor power related kernel or hardware configurations cpupower-monitor (1) - Report processor frequency and idle statistics cpupower-set (1) - Set processor power related kernel or hardware configurations cer@Telcontar:~> But of these I only see the manuals, not the tools :-? Sources are here: /usr/src/linux/tools/power/ Try "cpupower monitor" Most of the functionality fails here: Telcontar:~ # cpupower info System's multi core scheduler setting: not supported System's thread sibling scheduler setting: not supported System does not support Intel's performance bias setting analyzing CPU 0: Telcontar:~ Telcontar:~ # cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU boost state support: Supported: no Active: no Telcontar:~ # Even though I have an Intel CPU. :-? - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlcM2mIACgkQtTMYHG2NR9XeLACfS9+mhx+PfGTTOpjXGiLJOpP8 YIcAni2p0ZGuXx7EZE9lT0ksueYhsQWu =Hmnd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org