termux / termux/proot

[Bug]: malloc(): invalid size (unsorted) happened on galaxy s25ultra / proot-distro

Open
#313 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug report
Dominant language
C
Stars
1.1k
Forks
276
PR merge metrics
No merged PRs in 30d

Description

Problem description

tested termux ver: 118.2 / 119.0beta2
linux distro : archlinux arm (same img runs well on other devices : Motorola edge 40pro/ sd8gen2 (A13) ,ZTE nubia Z60ultra /sd8gen3 (A14)), Vivo iqoo neo 9pro /d9300 (A14) ,Sony Xperia 1 mk2 /sd864(A12)
I only have an 8elite cell phone running one ui7 / Android 15
I'm not sure if it's an Android issue or a Qualcomm chip issue or something else
I've tried multiple historical version mirrors from a few months ago and it all happens,So it shouldn't be a problem with archlinux rolling updates

Steps to reproduce the behavior.

time of occurrence:
archlinux booted,
1 :when i runing code-server 4.99.3 (or older edition),and when i connecting from browser,It happens probabilistically, and sometimes it can work fine。
2:when i open darktable (on LXDE ,VNC),
Error:free(): invalid next size (fast) Aborted
It happens the vast majority of the time,But it seems to have come up in the last two weeks。

For the time being, I have only encountered problems with these two programs, like firefox, qgis and other software I use is normal

What is the expected behavior?

No response

System information
  • Termux application version: 118.2 / 119.0beta2
  • Android OS version: 15
  • Device model: galaxy s25 ultra

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the allocator crash while connecting to code-server through a browser and while opening darktable under LXDE/VNC on the Galaxy S25 Ultra running Android 15. Compare those failures with the listed working devices and applications; done means isolating whether proot triggers the invalid allocation and documenting or resolving the reproducible cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c, linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.