)]}'
{
  "commit": "e4dab80e802241e416170b9686d8484eaa1f90f4",
  "tree": "f31268c1df8f71ccdce9e46df64eaf1569e0d11e",
  "parents": [
    "c8df23cb29146c1dfca82141e19b1049b1fc1011"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Sep 20 09:55:27 2011 +0000"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Sep 20 09:55:27 2011 +0000"
  },
  "message": "Fix of cpu hog in event pipe.\n\nIf client closed connection in ngx_event_pipe_write_to_downstream(), buffers\nin the \"out\" chain were lost.  This caused cpu hog if all available buffers\nwere in the \"out\" chain.  Fix is to call ngx_chain_update_chains() before\nchecking return code of output filter to avoid loosing buffers in the \"out\"\nchain.\n\nNote that this situation (all available buffers in the \"out\" chain) isn\u0027t\nnormal, it should be prevented by busy buffers limit.  Though right now it\nmay happen with complex protocols like fastcgi.  This should be addressed\nseparately.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "802c65ee99c2226b2a2392bf600b33d2e84be714",
      "old_mode": 33188,
      "old_path": "src/event/ngx_event_pipe.c",
      "new_id": "fb00bcc774156d9c21680eee370e27e2c705f2c5",
      "new_mode": 33188,
      "new_path": "src/event/ngx_event_pipe.c"
    }
  ]
}