public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manuel.lauss at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/30301] "memalign: Support scanning for aligned chunks" (24cdd6c71debfd10a9f7cb217fe2a2c4c486ed6f) causes regression in game "factorio" (malloc.c:3617 (_mid_memalign): assertion failed: ...)
Date: Tue, 11 Apr 2023 06:56:53 +0000 [thread overview]
Message-ID: <bug-30301-131-Elnw6S6Qno@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30301-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30301
--- Comment #4 from Manuel Lauss <manuel.lauss at gmail dot com> ---
(In reply to Manuel Lauss from comment #3)
> DJ's latest patch does fix the issue for me.
Ok I have to take that back: With DJ's fix applied on top of git head,
Factorio now works, but mpv/ffmpeg now throw this error on any video file:
(ffmpeg-5.1.2, apologies for the missing symbol names, but it should illustrate
the issue):
#0 0x00007ffff5d53bfc in () at /usr/lib64/libc.so.6
#1 0x00007ffff5d03572 in raise () at /usr/lib64/libc.so.6
#2 0x00007ffff5cec49f in abort () at /usr/lib64/libc.so.6
#3 0x00007ffff5ced3a4 in () at /usr/lib64/libc.so.6
#4 0x00007ffff5cfbba3 in () at /usr/lib64/libc.so.6
#5 0x00007ffff5d61b40 in () at /usr/lib64/libc.so.6
#6 0x00007ffff5d62102 in () at /usr/lib64/libc.so.6
#7 0x00007ffff5d6395d in posix_memalign () at /usr/lib64/libc.so.6
#8 0x00007ffff6663f0f in av_malloc () at /usr/lib64/libavutil.so.57
#9 0x00007ffff71490fa in () at /usr/lib64/libavcodec.so.59
#10 0x00007ffff7141d2f in () at /usr/lib64/libavcodec.so.59
#11 0x00007ffff7141ef8 in () at /usr/lib64/libavcodec.so.59
#12 0x00007ffff714cde6 in () at /usr/lib64/libavcodec.so.59
#13 0x00007ffff6e9cb6c in () at /usr/lib64/libavcodec.so.59
#14 0x00007ffff6eb9a04 in () at /usr/lib64/libavcodec.so.59
#15 0x00007ffff6f7d599 in avcodec_open2 () at /usr/lib64/libavcodec.so.59
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-11 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 12:31 [Bug malloc/30301] New: "memalign: Support scanning for aligned chunks" causes regression in game "factorio" manuel.lauss at gmail dot com
2023-04-02 18:42 ` [Bug malloc/30301] " sam at gentoo dot org
2023-04-02 18:42 ` [Bug malloc/30301] "memalign: Support scanning for aligned chunks" (24cdd6c71debfd10a9f7cb217fe2a2c4c486ed6f) causes regression in game "factorio" (malloc.c:3617 (_mid_memalign): assertion failed: !p || chunk_is_mmapped (mem2chunk (p)) || ar_ptr == arena_for_chunk (mem2chun sam at gentoo dot org
2023-04-02 18:42 ` [Bug malloc/30301] "memalign: Support scanning for aligned chunks" (24cdd6c71debfd10a9f7cb217fe2a2c4c486ed6f) causes regression in game "factorio" (malloc.c:3617 (_mid_memalign): assertion failed: ...) sam at gentoo dot org
2023-04-03 13:06 ` fweimer at redhat dot com
2023-04-03 18:50 ` crrodriguez at opensuse dot org
2023-04-03 19:01 ` dj at redhat dot com
2023-04-10 18:36 ` manuel.lauss at gmail dot com
2023-04-11 6:56 ` manuel.lauss at gmail dot com [this message]
2023-04-11 8:04 ` manuel.lauss at gmail dot com
2023-04-12 6:42 ` manuel.lauss at gmail dot com
2023-04-20 20:12 ` manuel.lauss at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-30301-131-Elnw6S6Qno@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).