Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • dailybuild_linux-x64
  • dailybuild_win32
  • websocket-haproxy
  • new_file_base
  • xjs-forum
  • revert-9d6b6c2f
  • mlong/darkmodetweak
  • 206-SlyEdit-NUL-timeout
  • web-mods
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
  • goodbuild_linux-x64_Aug-30-2020
  • goodbuild_linux-x64_Aug-29-2020
  • goodbuild_win32_Aug-29-2020
  • goodbuild_linux-x64_Aug-28-2020
  • goodbuild_win32_Aug-28-2020
  • goodbuild_linux-x64_Aug-27-2020
  • goodbuild_win32_Aug-27-2020
  • goodbuild_win32_Aug-26-2020
  • goodbuild_win32_Aug-25-2020
  • goodbuild_win32_Aug-24-2020
  • goodbuild_win32_Aug-23-2020
  • goodbuild_win32_Aug-22-2020
  • test
  • goodbuild_linux-x64_Aug-22-2020
30 results

cl-moar-objects.patch

Forked from Main / Synchronet
Source project has a limited visibility.
  • Deucе's avatar
    3adb964d
    Increase the Cyrptlib object limit from 1024 to 16384 · 3adb964d
    Deucе authored
    This may fix various out of resources issues.  Here's what the source
    has to say about this number:
    
    /* The maximum number of objects.  By default we use a fixed limit set to an
       appropriate large-enough value because the only time anyone that would
       really be creating thousands of objects is if they're leaking them and
       setting a fixed limit means this is detected without the code having to
       run for days or weeks leaking handles, however we allow a dynamically-
       configurable limit set via CONFIG_NUM_OBJECTS if someone really needs to
       use vast numbers of objects */
    3adb964d
    History
    Increase the Cyrptlib object limit from 1024 to 16384
    Deucе authored
    This may fix various out of resources issues.  Here's what the source
    has to say about this number:
    
    /* The maximum number of objects.  By default we use a fixed limit set to an
       appropriate large-enough value because the only time anyone that would
       really be creating thousands of objects is if they're leaking them and
       setting a fixed limit means this is detected without the code having to
       run for days or weeks leaking handles, however we allow a dynamically-
       configurable limit set via CONFIG_NUM_OBJECTS if someone really needs to
       use vast numbers of objects */