Skip to content
Snippets Groups Projects
Select Git revision
  • dd_area_choosers_split_string_infinite_loop_fix
  • dailybuild_linux-x64
  • dailybuild_win32
  • master default protected
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • 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
40 results

build

  • Clone with SSH
  • Clone with HTTPS
  • Deucе's avatar
    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 */
    a94344e9
    History
    Name Last commit Last update
    ..