> ## Documentation Index
> Fetch the complete documentation index at: https://cordial.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Cordial 0.14.1 — closing the game is no longer a crash

A patch release, mostly for one thing that was happening to everybody.

## Closing the window said Roblox had crashed

Because it had. The client segfaulted on the way out: the window was already
gone by the time Cordial next touched it, so every ordinary close ended on the
crash page. It exits cleanly now, three closes out of three.

## Cordial keeps older Roblox builds, and you can go back to one

When a Roblox update breaks something, you no longer have to wait it out.
Cordial keeps the current build and the two before it, and **Settings →
Version** lists them. Click one to use it for this profile, or press play to
use it and launch. "Follow the current build" puts things back.

Two things to know before relying on it. **Roblox refuses old clients
eventually**, on its own schedule, so a pinned build will stop working one day
and that will not be Cordial breaking. And a build is only kept whole if its
APK is on the same disk as Cordial's cache; one that is not is listed and
cannot be picked.

Builds you already had are moved into the new layout the first time you
launch. There is nothing to do.

## A new Roblox build no longer stops Cordial starting because of one C function

0.14.0 fixed `getpwuid_r` by adding it to a list. The list is no longer the
gate: Cordial reads what the engine actually imports and answers anything the
system's own C library has. That was
[#15](https://github.com/luohoa97/cordial/issues/15). A build that needs an
Android API with nothing behind it still fails, and says which one.

## What is still broken

**Resizing the window is glitchy for at least one person.** Not reproduced or
pinned down yet. If it happens to you, a screen recording and your compositor's
name would help more than anything.

**The TaskScheduler crash is still being reported** — `Can't initialize the
TaskScheduler before flags have been loaded`, this time on a second launch
after a first one worked. Three launches in a row here did not hit it. If you
do, the output of `cordial --diagnostics` and the full log are what is needed.

**Not yet seen on a screen**, so tell us if either is wrong: the update button
is meant to turn into a progress bar while Roblox downloads, and the black
squares in the window's rounded corners are meant to be gone.

Everything listed as broken in [0.14.0](/releases/v0.14.0) still is.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.