| Summary: | Crash when applying changes | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | pmanousis <pmanousis> |
| Component: | scene-opengl | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | Flags: | thomas.luebking:
Catalyst+
|
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | attachment-30998-0.html | ||
|
Description
pmanousis
2014-12-02 21:24:45 UTC
crashes in "eglCreateContext()" - do you attempt to use OpenGL 3.1? Try GL 2.0 instead and also please post the outout of "es2_info" It's however a driver bug. Hello,
Yes I have set it to OpenGL 3.1
I changed it to OpenGL 2.0 but I cannot find any application called es2_info.
By the way, I use the proprietary driver of amd.
On Tuesday 02 of December 2014 21:53:20 you wrote:
> https://bugs.kde.org/show_bug.cgi?id=341506
>
> Thomas Lübking <thomas.luebking@gmail.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Resolution|--- |UPSTREAM
> Status|UNCONFIRMED |RESOLVED
> Component|general |scene-opengl
>
> --- Comment #1 from Thomas Lübking <thomas.luebking@gmail.com> ---
> crashes in "eglCreateContext()" - do you attempt to use OpenGL 3.1?
> Try GL 2.0 instead and also please post the outout of "es2_info"
>
> It's however a driver bug.
Does it work with GL 2.0? es2_info is in the mesa-demos package, which may collide w/ fglrx (but i mostly wanted to know which gpu/driver and whether EGL works at all w/o crashing) Created attachment 89823 [details] attachment-30998-0.html Hello, it crashed again, using GL 2.0. Actually, I left my pc @home open while I am in my office and I sshed there and saw that the kded5 is using too much memory -which actually is increasing, too. Is there any memory leak? Before 3 hours it was about 400M and now it is 694M, according the htop tool. On Wed, Dec 3, 2014 at 12:32 AM, Thomas Lübking <thomas.luebking@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=341506 > > Thomas Lübking <thomas.luebking@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Flags| |Catalyst+ > > --- Comment #3 from Thomas Lübking <thomas.luebking@gmail.com> --- > Does it work with GL 2.0? > > es2_info is in the mesa-demos package, which may collide w/ fglrx (but i > mostly > wanted to know which gpu/driver and whether EGL works at all w/o crashing) > > -- > You are receiving this mail because: > You reported the bug. > (In reply to pmanousis from comment #4) > Hello, it crashed again, using GL 2.0. With the very same backtrace? > Actually, I left my pc @home open while I am in my office and I sshed there > and saw that the kded5 is using too much memory -which actually is > increasing, too. Is there any memory leak? Maybe, however: a) this is not related to kwin. A memory leak in kded would be in one of the daemons. You'd have to ideally isolate which one ("kcmshell5 kded" allows to toggle them) b) Increased memory usage does not necessarily imply a leak (ie. "lost" memory) c) "htop" is really no good reference to track memory usage (neither is top) - however notice that the relevant (ie. getting you a remote idea) field is "RES", "VIRT" includes shared memory as well as files mapped into the process memory (ie. also the file cache - the value is close to meaningless) To track whether your entire system increases memory usage, run grep MemAvailable /proc/meminfo If there's actually unusual memory usage in one process, a tool like "massif" (valgrind tool) or (brnad new ;-) "heaptrack"[1] allows to check why. [1] http://milianw.de/tag/heaptrack |