IRC Logs for #circuits Wednesday, 2015-07-01

*** travis-ci has joined #circuits07:47
travis-cicircuits/circuitsweb.github.io#3 (build - 2061c09 : James Mills): The build passed.07:47
travis-ciChange view : https://github.com/circuits/circuitsweb.github.io/compare/78f589dab1ae...2061c0904ea007:47
travis-ciBuild details : https://travis-ci.org/circuits/circuitsweb.github.io/builds/6909751807:47
*** travis-ci has left #circuits ()07:47
*** koobs has quit IRC07:49
*** travis-ci has joined #circuits08:27
travis-cicircuits/circuits.github.io#38 (build - ccc981d : James Mills): The build passed.08:27
travis-ciChange view : https://github.com/circuits/circuits.github.io/compare/b0afe9cbb7c5...ccc981d0bee108:27
travis-ciBuild details : https://travis-ci.org/circuits/circuits.github.io/builds/6910127708:27
*** travis-ci has left #circuits ()08:27
prologicy0no, so that fix has totally fixed your memory leak issues?08:44
prologicor is there still two more open issues08:44
prologicwait/fire08:44
*** travis-ci has joined #circuits09:18
travis-cicircuits/circuitsweb.github.io#5 (build - 4c33615 : James Mills): The build passed.09:18
travis-ciChange view : https://github.com/circuits/circuitsweb.github.io/compare/2061c0904ea0...4c336151651309:18
travis-ciBuild details : https://travis-ci.org/circuits/circuitsweb.github.io/builds/6910703309:18
*** travis-ci has left #circuits ()09:18
*** travis-ci has joined #circuits09:19
travis-cicircuits/circuits.github.io#39 (build - 3057eab : James Mills): The build passed.09:19
travis-ciChange view : https://github.com/circuits/circuits.github.io/compare/ccc981d0bee1...3057eabb20a409:19
travis-ciBuild details : https://travis-ci.org/circuits/circuits.github.io/builds/6910709109:19
*** travis-ci has left #circuits ()09:19
*** koobs has joined #circuits10:36
*** ninkotech has joined #circuits10:57
*** travis-ci has joined #circuits12:00
travis-cicircuits/circuitsweb.github.io#6 (build - b836170 : James Mills): The build passed.12:00
travis-ciChange view : https://github.com/circuits/circuitsweb.github.io/compare/4c3361516513...b836170992ba12:00
travis-ciBuild details : https://travis-ci.org/circuits/circuitsweb.github.io/builds/6912435012:00
*** travis-ci has left #circuits ()12:00
*** Coldblackice has quit IRC14:22
*** Zimsky-- has joined #circuits14:45
*** Zimsky has quit IRC14:46
*** riot has quit IRC14:46
*** riot has joined #circuits14:48
y0noprologic, I think the memory leak issue is not fixed15:29
y0notry treemo test: https://github.com/circuits/circuits/issues/54#issuecomment-10890934115:30
y0nowith the current version we consume more memory on call test than before15:30
y0nousing only 10 iterations on test seems to don't trigger the memory leak15:35
prologicmore?21:12
prologicwtf :)21:12
prologicI fixed a very obvious leak21:12
prologicOkay I'll keep investigating21:12
prologicthanks for your help and testing y0no21:13
y0noI think that the current memory_leak test pass, because we only try 10 fire/call. It's not enough to see the memory growing. If I remember well, python reserve memory block and grow if the previous block is full. I think that 10 iterations is not enough to reserve a new block.21:16
prologicahh okay21:17
prologicI set it at 10 because I did notice we were leaking adding dynamic event handlers for .call()21:18
prologicbut there are likely a few other things going on21:18
y0nookay21:30
prologicwhat was the fix you mentioned that fixed some small part that you found?21:40
prologiccould you add it as a comment to #54?21:40
*** Coldblackice has joined #circuits22:18

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!