[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 GitLab Migration User changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #46 from rol...@rptd.ch --- (In reply to Marek Olšák from comment #21) > How do I reproduce it? Looks like the trace file is too large to be attached here. I've put the file on my server to access: http://rptd.ch/misc/debug/deigde.t

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #45 from rol...@rptd.ch --- That was now really rude. Anyways. I'm interested in a solution, not discussion so I've pulled an apitrace of the situation. This does reproduce the problem. It's though 60M in size. Compressed it's 8M. Ca

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 Matt Turner changed: What|Removed |Added CC|matts...@gmail.com | --- Comment #44 from Matt Turner --- (I

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #43 from rol...@rptd.ch --- Sorry, but this is rude. I waited for an answer on my result of testing the patch (as requested) and that's what I get as answer? I can continue trying to find a reproducible task but then please say that

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #42 from Matt Turner --- (In reply to rol...@rptd.ch from comment #41) > EDIT: to sum up: > 1) GIT master + patch => bug present > 2) GIT master - patch + revert-commit => bug fixed If you don't have a way for developers to reproduc

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #41 from rol...@rptd.ch --- EDIT: to sum up: 1) GIT master + patch => bug present 2) GIT master - patch + revert-commit => bug fixed -- You are receiving this mail because: You are the assignee for the bug._

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #40 from rol...@rptd.ch --- I tested the patch now against the master GIT from mesa. It makes no difference. RAM consumption still sky-rockets and application then crashes. -- You are receiving this mail because: You are the assign

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #39 from Matt Turner --- (In reply to rol...@rptd.ch from comment #38) > Could it be that your patch is not for version "mesa-19.0.8" as I'm using? > (newer ones are keyworded) Perhaps try 19.2.0_rc3. That's much closer to master.

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-12 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #38 from rol...@rptd.ch --- Could it be that your patch is not for version "mesa-19.0.8" as I'm using? (newer ones are keyworded) -- You are receiving this mail because: You are the assignee for the bug.

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #36 from rol...@rptd.ch --- # mkdir -p /etc/portage/patches/media-libs/mesa/ # cd /etc/portage/patches/media-libs/mesa/ wget 'https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1852.patch' --2019-09-11 18:35:51-- https://gitlab

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #37 from Matt Turner --- (In reply to rol...@rptd.ch from comment #36) > # mkdir -p /etc/portage/patches/media-libs/mesa/ > # cd /etc/portage/patches/media-libs/mesa/ > wget 'https://gitlab.freedesktop.org/mesa/mesa/merge_requests/18

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #35 from Matt Turner --- (In reply to rol...@rptd.ch from comment #34) > I do not see anything mentioned there. I've wget the file into > /etc/portage/patches/media-libs/mesa/ directory, which did not exist. > Anything else I need to

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #34 from rol...@rptd.ch --- I do not see anything mentioned there. I've wget the file into /etc/portage/patches/media-libs/mesa/ directory, which did not exist. Anything else I need to do to get Gentoo to pick up the patch? -- You

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #33 from Matt Turner --- It will show the patch being applied before configuration. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #32 from rol...@rptd.ch --- Is there a way I can verify the rebuilding has picked up the patch file? I rebuild and started the application but the result is the same. Now I'm not sure if the patch is not working or not picked up prop

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #31 from Matt Turner --- (In reply to rol...@rptd.ch from comment #30) > How I best test this? Just check out the branch and build it or apply it > somehow to the mesa branch I have here from bisecting? wget 'https://gitlab.freedesk

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #30 from rol...@rptd.ch --- How I best test this? Just check out the branch and build it or apply it somehow to the mesa branch I have here from bisecting? -- You are receiving this mail because: You are the assignee for the bug.__

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #29 from Timothy Arceri --- (In reply to rol...@rptd.ch from comment #22) > Hi Marek, > > This is going to be complicated. The application is not yet free to use by > others (working on getting it to release shape). I would have to

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #28 from rol...@rptd.ch --- I had deleted the cache already so I doubt this is the problem. I tried pulling all the shaders and trying to make a small console app just compiling them but so far no luck. I guess I need to check out th

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #27 from Matt Turner --- Is the shader-cache causing the shaders to be loaded from disk instead of compiled? Try with the environment variable MESA_GLSL_CACHE_DISABLE=1 -- You are receiving this mail because: You are the assignee

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #26 from rol...@rptd.ch --- I've tried getting something done with RenderDoc but I did not get anywhere. I can capture the scene in the application (basically just a sky-box) but that's not really helpful. The problem happens while s

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #25 from Matt Turner --- (In reply to rol...@rptd.ch from comment #24) > (In reply to Matt Turner from comment #23) > > Can you make an apitrace of the application that demonstrates the problem? > > I can only try RenderDoc. But can

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #24 from rol...@rptd.ch --- (In reply to Matt Turner from comment #23) > Can you make an apitrace of the application that demonstrates the problem? I can only try RenderDoc. But can you export an API trace with it? -- You are rece

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #23 from Matt Turner --- Can you make an apitrace of the application that demonstrates the problem? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-09-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #22 from rol...@rptd.ch --- Hi Marek, This is going to be complicated. The application is not yet free to use by others (working on getting it to release shape). I would have to figure out first how to break this down into a reprodu

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-08-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #21 from Marek Olšák --- How do I reproduce it? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https:/

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-08-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 Matt Turner changed: What|Removed |Added CC||mar...@gmail.com Keywords|

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-08-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #19 from rol...@rptd.ch --- Need to shift this back to GenToo since compiling (aka bisecting) is not the problem right now but GenToo (which actually is the "only" distro I've seen this problem on so far). -- You are receiving this

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-08-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 Matt Turner changed: What|Removed |Added CC||matts...@gmail.com --- Comment #18 from M

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-08-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #17 from Matt Turner --- The build failure is in Clover, the OpenCL implementation. If the application that triggers the huge amount of RAM problem is not using OpenCL, disable OpenCL in meson configure and try to get past that. --

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-08-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #16 from rol...@rptd.ch --- Created attachment 145083 --> https://bugs.freedesktop.org/attachment.cgi?id=145083&action=edit Linking fail log -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-08-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #15 from rol...@rptd.ch --- I've tried now the patching approach. I had to patch in total three files: src/amd/common/ac_nir_to_llvm.c src/gallium/auxiliary/gallivm/lp_bld_init.c src/gallium/drivers/radeonsi/si_shader_tgsi_setup.c

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-26 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #14 from Matt Turner --- (In reply to rol...@rptd.ch from comment #13) > I checked out the 18.2 branch which I assume should work (if the theory is > correct). > > Modifying files won't work with bisecting, right? You'll probably h

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #13 from rol...@rptd.ch --- I checked out the 18.2 branch which I assume should work (if the theory is correct). Modifying files won't work with bisecting, right? -- You are receiving this mail because: You are the assignee for th

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #12 from Matt Turner --- (In reply to rol...@rptd.ch from comment #11) > ../src/amd/common/ac_nir_to_llvm.c > ../src/amd/common/ac_nir_to_llvm.c: In function ‘ac_llvm_finalize_module’: > ../src/amd/common/ac_nir_to_llvm.c:6614:2: err

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #11 from rol...@rptd.ch --- Unfortunately it does not compile like this: FAILED: src/amd/common/2a96a08@@amd_common@sta/ac_nir_to_llvm.c.o cc -Isrc/amd/common/2a96a08@@amd_common@sta -Isrc/amd/common -I../src/amd/common -Isrc/../in

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #10 from Matt Turner --- (In reply to rol...@rptd.ch from comment #9) > I get two config attempts. This is the second one. Do you see anything out > of place here? > > meson --buildtype plain --libdir lib64 --localstatedir /var/lib

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #9 from rol...@rptd.ch --- I get two config attempts. This is the second one. Do you see anything out of place here? meson --buildtype plain --libdir lib64 --localstatedir /var/lib --prefix /usr --sysconfdir /etc --wrap-mode nodownl

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #8 from Matt Turner --- (In reply to rol...@rptd.ch from comment #4) > I tried compiling from source but it does not work. Seems to have troubles > with libdrm. > > configure: error: Package requirements (libdrm >= 2.4.75 libdrm_int

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #7 from rol...@rptd.ch --- I'm on GenToo. It's a source based distro thus every package installed has headers and libraries installed too otherwise the distro won't work. So I'm positive everything required for compiling mesa is ther

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #6 from Timothy Arceri --- (In reply to rol...@rptd.ch from comment #4) > I tried compiling from source but it does not work. Seems to have troubles > with libdrm. > > configure: error: Package requirements (libdrm >= 2.4.75 libdrm_

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-12 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #5 from rol...@rptd.ch --- For the records: installed version is 2.4.97 -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-12 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #4 from rol...@rptd.ch --- I tried compiling from source but it does not work. Seems to have troubles with libdrm. configure: error: Package requirements (libdrm >= 2.4.75 libdrm_intel >= 2.4.75) were not met: Can't seem to get pas

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #3 from Timothy Arceri --- Are you able to build mesa from git and do a git bisect to find the problem commit? -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #2 from rol...@rptd.ch --- I don't know what other information can help so I collected information about the state that worked (before the update) and the state that does not work anymore (after the update): before update (working s

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 --- Comment #1 from rol...@rptd.ch --- I've started the application now also in a debugger and went to loading a simple model which causes tons of RAM to be consumes by the shader compiler. I interrupted with GDB and made a trace: #0 0x7f65

[Bug 111077] link_shader and deserialize_glsl_program suddenly consume huge amount of RAM

2019-07-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111077 Bug ID: 111077 Summary: link_shader and deserialize_glsl_program suddenly consume huge amount of RAM Product: Mesa Version: 18.3 Hardware: x86-64 (AMD64) O