[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=363749

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||k...@davidedmundson.co.uk
 Status|UNCONFIRMED |RESOLVED

--- Comment #16 from David Edmundson  ---
Yes, that shader is fixed for GLES. 

But OPs setup is also being weird for no reason.

Though it's weird that stderr allegedly causes memory to go up. That shouldn't
happen.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Alexander Mentyu]

https://bugs.kde.org/show_bug.cgi?id=363749

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #15 from Alexander Mentyu  ---
Can this issue safely be closed?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=363749

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #14 from Martin Gräßlin  ---
We don't need to discuss this

The problem that users have incorrectly Gles is always gentoo. Guess why I
immediately jumped to the conclusion that you use Gentoo.

Gles an gl are not mutual exclusive in the system. But in Qt they are.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #13 from s...@zxc.pp.ua ---
(In reply to Martin Gräßlin from comment #12)

> No, is an old Linux myth. Just think about it, that wouldn't work anywhere,
> no distro compiles with gles.
> 
> This problem only exists for Gentoo users.

It's not true :).

dev-libs/efl:

configure: error: Full OpenGL with EGL is not supported, please add
--with-opengl=es to your configure 
options to switch to EGL + OpenGL ES.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #12 from Martin Gräßlin  ---
Am 18. Januar 2017 22:43:31 MEZ schrieb bugzilla_nore...@kde.org:
>https://bugs.kde.org/show_bug.cgi?id=363749
>
>--- Comment #11 from s...@zxc.pp.ua ---
>(In reply to Martin Gräßlin from comment #10)
>> > wayland and other DEs which require gles.
>> 
>> Wayland does not (!) require GLES.
>
>Wayland by itself not require gles. But other DEs require gles to run
>(compile)
>with wayland support.

No, is an old Linux myth. Just think about it, that wouldn't work anywhere, no
distro compiles with gles.

This problem only exists for Gentoo users.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #11 from s...@zxc.pp.ua ---
(In reply to Martin Gräßlin from comment #10)
> > wayland and other DEs which require gles.
> 
> Wayland does not (!) require GLES.

Wayland by itself not require gles. But other DEs require gles to run (compile)
with wayland support.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Simon Andric]

https://bugs.kde.org/show_bug.cgi?id=363749

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #10 from Martin Gräßlin  ---
> wayland and other DEs which require gles.

Wayland does not (!) require GLES.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #9 from s...@zxc.pp.ua ---
By the way kscreenlocker is only program (installed on my computer) that
causing such memory leak.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #8 from s...@zxc.pp.ua ---
(In reply to Martin Gräßlin from comment #6)
> > 98% sure that answer is yes.
> 
> If it is: switch to normal OpenGL (in case you are a Gentoo user this
> requires a full(!) rebuild of everything of Qt and everything depending on
> Qt). OpenGL ES is not (!) intended to be used on normal desktop systems. The
> memory leak you are experience might be a side effect of the broken OpenGL
> setup.

Thanks, I'll try. But I'm not sure that it will be ok, because sometimes I test
wayland and other DEs which require gles. And as far as I remember on some
packages emerge requires choosing one of opengl or gles.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #7 from Martin Gräßlin  ---
And yes, the valgrind log shows you are using OpenGL ES and it's full of errors
due to that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #6 from Martin Gräßlin  ---
> 98% sure that answer is yes.

If it is: switch to normal OpenGL (in case you are a Gentoo user this requires
a full(!) rebuild of everything of Qt and everything depending on Qt). OpenGL
ES is not (!) intended to be used on normal desktop systems. The memory leak
you are experience might be a side effect of the broken OpenGL setup.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #5 from s...@zxc.pp.ua ---
(In reply to Martin Gräßlin from comment #4)
> Are you using an OpenGL es build of Qt?

98% sure that answer is yes. I can check check it tomorrow.

I saw bug somewhere around regarding qt + gles and "error: program lacks a
fragment shader", but it seems that there were no information about memory
leaks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Martin Gräßlin]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #4 from Martin Gräßlin  ---
Are you using an OpenGL es build of Qt?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #3 from s...@zxc.pp.ua ---
Created attachment 103490
  --> https://bugs.kde.org/attachment.cgi?id=103490=edit
valgrind kscreen log for 1 minute

Attaching valgrind log

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=363749

s...@zxc.pp.ua changed:

   What|Removed |Added

 CC||s...@zxc.pp.ua

--- Comment #2 from s...@zxc.pp.ua ---
I can confirm this bug. It's still appear with kscreenlocker versions 5.8.3 -
5.8.5.

Memory leak amount is ~ 250mB per hour. 

In testing mode it produce:

***
QOpenGLShader::link: error: program lacks a fragment shader

shader compilation failed: 
"error: program lacks a fragment shader\n"
QOpenGLShader::link: error: program lacks a fragment shader

QOpenGLShader::compile(Fragment): 0:6(2): error: No precision specified in this
scope for type `vec4'
0:7(2): error: No precision specified in this scope for type `float'
0:8(2): error: No precision specified in this scope for type `float'
0:9(2): error: No precision specified in this scope for type `float'
0:9(22): error: initializer of global variable `outerRadius' must be a constant
expression
0:10(2): error: No precision specified in this scope for type `vec4'
0:13(2): error: No precision specified in this scope for type `vec4'
0:15(2): error: No precision specified in this scope for type `vec2'
0:16(2): error: No precision specified in this scope for type `float'

*** Problematic Fragment shader source code ***
#ifndef GL_FRAGMENT_PRECISION_HIGH
#define highp mediump
#endif
#line 1

varying highp vec2 qt_TexCoord0;
uniform highp float qt_Opacity;
uniform lowp sampler2D source;

uniform vec4 colorBorder;
float blend = 0.01;
float innerRadius = 0.47;
float outerRadius = innerRadius + 0.02;
vec4 colorEmpty = vec4(0.0, 0.0, 0.0, 0.0);

void main() {
vec4 colorSource = texture2D(source,
qt_TexCoord0.st);

vec2 m = qt_TexCoord0 - vec2(0.5, 0.5);
float dist = sqrt(m.x * m.x + m.y * m.y);

if (dist < innerRadius)
gl_FragColor = colorSource;
else if (dist < innerRadius + blend)
gl_FragColor = mix(colorSource, colorBorder,
((dist - innerRadius) / blend));
else if (dist < outerRadius)
gl_FragColor = colorBorder;
else if (dist < outerRadius + blend)
gl_FragColor = mix(colorBorder, colorEmpty,
((dist - outerRadius) / blend));
else
gl_FragColor = colorEmpty ;

gl_FragColor = gl_FragColor * qt_Opacity;
}

***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363749

--- Comment #1 from Martin Gräßlin  ---
you can run the actual binary of kscreenlocker_greet with --testing through gdb
or valgrind. Though there is a chance that the actual problem won't be hit when
in test mode.

-- 
You are receiving this mail because:
You are watching all bug changes.