Artifactspublic-v0

curl

master
ply4 git calls213 ms288 KiB2 cachedprotocol v2
82 lines2.1 KiBRaw

NAME

curl_global_cleanup - global libcurl cleanup

SYNOPSIS

c
#include <curl/curl.h>

void curl_global_cleanup(void);

DESCRIPTION

This function releases resources acquired by curl_global_init(3).

You should call curl_global_cleanup(3) once for each call you make to curl_global_init(3), after you are done using libcurl.

This function is thread-safe since libcurl 7.84.0 if curl_version_info(3) has the CURL_VERSION_THREADSAFE feature bit set (most platforms).

If this is not thread-safe, you must not call this function when any other thread in the program (i.e. a thread sharing the same memory) is running. This does not only mean other threads that use libcurl. Because curl_global_cleanup(3) calls functions of other libraries that are similarly thread-unsafe, it could conflict with any other thread that uses these other libraries.

See the description in libcurl(3) of global environment requirements for details of how to use this function.

CAUTION

curl_global_cleanup(3) does not block waiting for any libcurl-created threads to terminate (such as threads used for name resolving). If a module containing libcurl is dynamically unloaded while libcurl-created threads are still running then your program may crash or other corruption may occur. We recommend you do not run libcurl from any module that may be unloaded dynamically. This behavior may be addressed in the future.

libcurl may not be able to fully clean up after multi-threaded OpenSSL depending on how OpenSSL was built and loaded as a library. It is possible in some rare circumstances a memory leak could occur unless you implement your own OpenSSL thread cleanup. Refer to libcurl-thread(3).

%PROTOCOLS%

EXAMPLE

c
int main(void)
{
  curl_global_init(CURL_GLOBAL_DEFAULT);

  /* use libcurl, then before exiting... */

  curl_global_cleanup();
}

%AVAILABILITY%

RETURN VALUE

None

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Title: curl_global_cleanup
5Section: 3
6Source: libcurl
7See-also:
8 - curl_global_init (3)
9 - libcurl (3)
10 - libcurl-thread (3)
11Protocol:
12 - All
13Added-in: 7.8
14---
16# NAME
18curl_global_cleanup - global libcurl cleanup
20# SYNOPSIS
22~~~c
23#include <curl/curl.h>
25void curl_global_cleanup(void);
26~~~
28# DESCRIPTION
30This function releases resources acquired by curl_global_init(3).
32You should call curl_global_cleanup(3) once for each call you make to
33curl_global_init(3), after you are done using libcurl.
35This function is thread-safe since libcurl 7.84.0 if
36curl_version_info(3) has the CURL_VERSION_THREADSAFE feature bit set
37(most platforms).
39If this is not thread-safe, you must not call this function when any other
40thread in the program (i.e. a thread sharing the same memory) is running. This
41does not only mean other threads that use libcurl. Because
42curl_global_cleanup(3) calls functions of other libraries that are similarly
43thread-unsafe, it could conflict with any other thread that uses these other
44libraries.
46See the description in libcurl(3) of global environment requirements for
47details of how to use this function.
49# CAUTION
51curl_global_cleanup(3) does not block waiting for any libcurl-created
52threads to terminate (such as threads used for name resolving). If a module
53containing libcurl is dynamically unloaded while libcurl-created threads are
54still running then your program may crash or other corruption may occur. We
55recommend you do not run libcurl from any module that may be unloaded
56dynamically. This behavior may be addressed in the future.
58libcurl may not be able to fully clean up after multi-threaded OpenSSL
59depending on how OpenSSL was built and loaded as a library. It is possible in
60some rare circumstances a memory leak could occur unless you implement your own
61OpenSSL thread cleanup. Refer to libcurl-thread(3).
63# %PROTOCOLS%
65# EXAMPLE
67~~~c
68int main(void)
70 curl_global_init(CURL_GLOBAL_DEFAULT);
72 /* use libcurl, then before exiting... */
74 curl_global_cleanup();
76~~~
78# %AVAILABILITY%
80# RETURN VALUE
82None
Diagnostics4 git calls · 213 ms
CallStatusSizeTime0213 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit4 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=206
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=4
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2001.1 KiB206 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=1176
git.response.cache=MISS
git.response.duration_ms=206
git.fetch.wants=e6f8e42fd7c444c12b40d8833cfacb5bb33dca7a
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=1176
git.pkt.payload.max=1155
git.sideband.band1.bytes=1154
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e176a42ccc2a7e
Request
856ba3e9…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format