<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Constantly increasing memory consumption in JavaFX applications" href="https://bugs.freedesktop.org/show_bug.cgi?id=98831#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Constantly increasing memory consumption in JavaFX applications" href="https://bugs.freedesktop.org/show_bug.cgi?id=98831">bug 98831</a> from <a class="email" href="mailto:itaisha@gmail.com" title="Itai <itaisha@gmail.com>"> Itai</a> <pre>I'm running on Intel HD4000 graphics (i5-3210M integrated GPU). I believe I'm using the i965 driver, or whatever is the default on Debian systems. Here are what I believe to be the relevant lines from my Xorg.log file: [ 89791.660] (II) LoadModule: "intel" [ 89791.660] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 89791.661] (II) Module intel: vendor="X.Org Foundation" [ 89791.661] compiled for 1.17.2, module version = 2.99.917 [ 89791.661] Module class: X.Org Video Driver [ 89791.661] ABI class: X.Org Video Driver, version 19.0 [ 89791.661] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 89791.661] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [ 89791.661] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [ 89791.661] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 [ 89791.661] (++) using VT number 7 [ 89791.661] (WW) xf86OpenConsole: setpgid failed: Operation not permitted [ 89791.661] (WW) xf86OpenConsole: setsid failed: Operation not permitted [ 89791.662] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20150327 [ 89791.662] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.917-2 (Vincent Cheng <<a href="mailto:vcheng@debian.org">vcheng@debian.org</a>>) [ 89791.662] (II) intel(0): SNA compiled for use with valgrind [ 89791.662] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4000 [ 89791.662] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx If there is a better way of verifying what driver I'm using please let me know. The problem disappears completely when using SW rendering in Java (-Dprism.order=sw), which as far as I understand surpasses Mesa, but I'm not sure. I'm not sure what Apitrace is or how to make/run one. If you can provide a link to an explanation I'll be happy to try it. I have made a valgrind output in the past, but even gzipped it's too big to attach here (~110KB, the limit seems to be 32KB). I don't know if it is of any help, but the last lines are attached here: ==18204== 16,793,616 bytes in 1 blocks are possibly lost in loss record 6,235 of 6,237 ==18204== at 0x4C2BBCF: malloc (vg_replace_malloc.c:299) ==18204== by 0x2A344779: _swrast_CreateContext (s_context.c:775) ==18204== by 0x2A5267BA: brwCreateContext (brw_context.c:937) ==18204== by 0x2A4C0749: driCreateContextAttribs (dri_util.c:448) ==18204== by 0x2492241E: dri3_create_context_attribs (dri3_glx.c:300) ==18204== by 0x249224D2: dri3_create_context (dri3_glx.c:329) ==18204== by 0x248F0D8A: CreateContext (glxcmds.c:300) ==18204== by 0x248F1466: glXCreateNewContext (glxcmds.c:1657) ==18204== by 0x218CE714: Java_com_sun_prism_es2_X11GLContext_nInitialize (in /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libprism_es2.so) ==18204== by 0x86A4753: ??? ==18204== by 0x8694B0F: ??? ==18204== by 0x8694FFC: ??? ==18204== ==18204== LEAK SUMMARY: ==18204== definitely lost: 360,619 bytes in 92 blocks ==18204== indirectly lost: 37,197 bytes in 243 blocks ==18204== possibly lost: 24,622,035 bytes in 12,137 blocks ==18204== still reachable: 221,213,543 bytes in 7,097,256 blocks ==18204== of which reachable via heuristic: ==18204== length64 : 5,088 bytes in 72 blocks ==18204== newarray : 24,296 bytes in 31 blocks ==18204== suppressed: 0 bytes in 0 blocks ==18204== Reachable blocks (those to which a pointer was found) are not shown. ==18204== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==18204== ==18204== For counts of detected and suppressed errors, rerun with: -v ==18204== Use --track-origins=yes to see where uninitialised values come from ==18204== ERROR SUMMARY: 896128 errors from 2567 contexts (suppressed: 0 from 0) Note that at the time of closing the program the usage exceeded 3GB, which from what I understand is far more than the leak summary shows. I have not tried this with git/13, I may be able to do so later.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>