29314690c7
The amount of used memory should stay in relation to the number of entries we have. If we delete most (75%) of the entries, let's also reallocate the buffer down to 50% of its size. datalist_append() now starts with 2 elements. This works together with the shrinking. If we only have one entry left, we will shrink the buffer back to size 2. In general, d->alloc is always a power of two (unless it overflows after G_MAXUINT32/2, which we assume will never happen). The previous buffer growth strategy of never shrinking is not necessarily bad. It has the advantage to not require any checks for shrinking, and it works well in cases where the amount of data actually does not shrink (as we'd often expect). Also, it's questionable what a realloc() to a smaller size really brings. Is that really gonna help and will the allocator do something useful? Anyway. This patch introduces shrinking. The check for whether to shrink changes from `if (d->len == 0)` to `if (d->len <= d->alloc / 4u)`, which is probably cheap even if most of the time we don't need to shrink. For most cases, that's the only change that this patch brings. However, once we find out that 75% of the buffer are empty, calling realloc() seems a sensible thing to do.
GLib
GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.
The official download locations are: https://download.gnome.org/sources/glib
The official web site is: https://www.gtk.org/
Installation
See the file ‘INSTALL.md’. There is separate and more in-depth documentation for building GLib on Windows.
Supported versions
Upstream GLib only supports the most recent stable release series, the previous stable release series, and the current development release series. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.
See SECURITY.md for more details.
Documentation
API documentation is available online for GLib for the:
Discussion
If you have a question about how to use GLib, seek help on GNOME’s Discourse
instance. Alternatively, ask a question
on StackOverflow and tag it glib.
Reporting bugs
Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.
Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.
In bug reports please include:
- Information about your system. For instance:
- What operating system and version
- For Linux, what version of the C library
- And anything else you think is relevant.
- How to reproduce the bug.
- If you can reproduce it with one of the test programs that are built
in the
tests/subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
- If you can reproduce it with one of the test programs that are built
in the
- If the bug was a crash, the exact text that was printed out when the crash occurred.
- Further information such as stack traces may be useful, but is not necessary.
Contributing to GLib
Please follow the contribution guide to know how to start contributing to GLib.
Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):
Closes: #123
Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.