{"push_id":696332674,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"76169cc2c4409199b97c7029de071ec2f3c2c2c2","before":"e31b6d2771033bef1383f0d24a8b5fbf4fa10890","commits":[{"sha":"5a9c731d44c17dfb90779afb8d0b6fe242cf56be","author":{"email":"fe9e26f3989304bf7275ed139c57fd059c63d22d@chromium.org","name":"Bruce Dawson"},"message":"Rename Readme.txt in project file and update contents.\n\nThe UIforETW project referenced ReadMe.txt but that file was long\nago renamed to ReadMe.md, so I updated the reference.\n\nI also deleted two lines for tasks that are no longer needed:\n- The bug with .txt files being left behind seems to be gone.\n- The use of github releases means that there is no longer any need\nfor an installer to install the MFC DLLs.","distinct":true,"url":"https://api.github.com/repos/google/UIforETW/commits/5a9c731d44c17dfb90779afb8d0b6fe242cf56be"},{"sha":"1fe6007770c158de13fda4aa45eef5134a0c1a98","author":{"email":"fe9e26f3989304bf7275ed139c57fd059c63d22d@chromium.org","name":"Bruce Dawson"},"message":"Disable the key logger thread when debugging to avoid hangs.\n\nWhen debugging UIforETW there have always been hangs - whenever\nUIforETW is paused in the debugger the entire system would take\nabout ten seconds to respond to input. This makes single-stepping\npainful and alt+tabbing impossible.\n\nI finally realized that this was caused by the input hooks. When\nUIforETW is paused in the debugger the input hook thread can't\nrespond in a timely manner and the system has to timeout on each\ninput, about ten seconds at a time.\n\nI now disable the input hook thread when a debugger is present at\nstartup.","distinct":true,"url":"https://api.github.com/repos/google/UIforETW/commits/1fe6007770c158de13fda4aa45eef5134a0c1a98"},{"sha":"b1dae28893b4cdd22777818875ee653aade6e44a","author":{"email":"fe9e26f3989304bf7275ed139c57fd059c63d22d@chromium.org","name":"Bruce Dawson"},"message":"Automatically use more trace buffers on machines that can afford it.\n\nWhen tracing to a file it makes sense to have as many buffers as\npossible to make sure that events do not get lost. With this change\nthe default buffer count is increased by 50% to 100% on machines with\n15+ GB and 30+ GB respectively, using the new BufferCountBoost\nfunction.\n\nAdding this functionality necessitated stringPrintf which is a\ngenerally handy function anyway. While adding that I added debugPrint\nfor printing to outputDebugString.\n\nTracing to memory is not affected - the buffer count there should\nbe user controlled to allow controlling the size of the resultant\ntraces.","distinct":true,"url":"https://api.github.com/repos/google/UIforETW/commits/b1dae28893b4cdd22777818875ee653aade6e44a"},{"sha":"76169cc2c4409199b97c7029de071ec2f3c2c2c2","author":{"email":"fe9e26f3989304bf7275ed139c57fd059c63d22d@chromium.org","name":"Bruce Dawson"},"message":"Remove commented out IsWindowsServer() function.","distinct":true,"url":"https://api.github.com/repos/google/UIforETW/commits/76169cc2c4409199b97c7029de071ec2f3c2c2c2"}]}