Question 1

How to fix Ladybird RequestServer crashing on startup with “database disk image is malformed”?

Accepted Answer

The HTTP disk cache database is corrupted. Close Ladybird, then delete the cache directory and restart:

```sh
rm -rf ~/.cache/Ladybird
```

If you set a custom cache location, delete `$XDG_CACHE_HOME/Ladybird` instead. Ladybird will rebuild the cache automatically. Removing `~/.config/Ladybird` is not necessary because that stores configuration, not the disk cache.

A code fix in newer builds propagates `CacheIndex` initialization errors instead of crashing RequestServer, but clearing the corrupted cache remains the immediate workaround.

Question 2

Why does Ladybird show "Unable to resolve host" after the first page load when using Pi-hole or a custom DNS server?

Accepted Answer

This is caused by expired DNS address records remaining in Ladybird's cache. With very short TTLs, the A/AAAA record can expire while the parent CNAME record is still cached, so a later lookup follows the CNAME but finds no usable IP address. The fix is the LibDNS/RequestServer change titled "Forget about fully expired RRs" (fixes issue #12215). Update Ladybird to a build containing that fix and rebuild, for example with `git pull && ./Meta/ladybird.py run`. As a temporary workaround, go to `about:settings` → Network, switch from Custom DNS to the system/default resolver, and restart Ladybird.

Question 3

How to fix Ladybird SIGILL at ICU.h:104 when Intl.NumberFormat.formatRangeToParts receives an empty array?

Accepted Answer

This crash is triggered by `Intl.NumberFormat().formatRangeToParts(0, [])`. Ladybird passes the empty array to ICU decimal conversion, ICU returns `U_DECIMAL_NUMBER_SYNTAX_ERROR`, and `verify_icu_success()` in `ICU.h:104` aborts with `SIGILL` instead of producing a JavaScript-level completion.

Fix: update/rebuild Ladybird to a version containing the PR "LibUnicode+LibJS: Throw instead of aborting on Intl input ICU refuses." The patch prevents invalid ICU input from crashing the native runtime.

Workaround on affected builds: convert both endpoints to JavaScript numbers before calling the API, since `Number([])` is `0`:

```js
const nf = new Intl.NumberFormat();
nf.formatRangeToParts(Number(0), Number([]));
```

Or in a wrapper:

```js
function safeFormatRangeToParts(nf, start, end) {
    return nf.formatRangeToParts(Number(start), Number(end));
}
```

Do not pass arrays or other non-primitive endpoints directly to affected Ladybird versions.

Question 4

How to fix Ladybird crashing when DevTools disconnects with `VERIFY(m_devtools_client_count > 0)`?

Accepted Answer

This crash occurs because DevTools client state can get out of sync with the tab's current page, especially when attaching DevTools to a page such as `mail.google.com`. It is fixed by the LibWebView/LibWeb change that keeps DevTools state synchronized with the tab's page. Upgrade Ladybird to a release or build containing that fix. As a workaround on Ladybird 1.0, avoid attaching or repeatedly disconnecting DevTools from the affected tab and restart Ladybird after the crash.

Question 5

Why is the "Read more" button missing for long YouTube comments in Ladybird?

Accepted Answer

This is caused by Ladybird's old `-webkit-line-clamp` implementation: clamped content was not included in scrollable overflow, so `scrollHeight` incorrectly returned the same value as `clientHeight`. YouTube uses these values to detect truncated comments, so it assumed there was nothing to expand and hid the "Read more" button. The Battery Status API errors in the console are unrelated. The fix is the LibWeb change "Keep clamped `-webkit-line-clamp` content in scrollable overflow," which lays out and measures the hidden clamped content like Firefox does. Update Ladybird to a build containing that PR and rebuild. As a temporary workaround, open the video/comment in Firefox or another browser.

ladybird

Overview

README Preview

FAQ (5)

同类型项目

vscode

FreeDomain

stable-diffusion-webui

paperclip