Date: Thu, 13 Nov 2025 11:38:08 +0100 From: Michal Meloun <mmel@FreeBSD.org> To: Ronald Klop <ronald@FreeBSD.org>, Carl Shapiro <cshapiro@panix.com> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Message-ID: <10c8be48-e9cd-4574-868f-51b113159311@FreeBSD.org> In-Reply-To: <5dd66c4c-ed4d-4034-9fb3-f9079a513595@FreeBSD.org> References: <aOu7s9roGCofdCOw@www.zefox.net> <aOvTG-20QRJtJJwf@int21h> <CANCZdfrJ8rph_rkT3Mk-sNYKNspoV15SvHWLsahzS0HnULi4ww@mail.gmail.com> <aO068RrAehdiHOoZ@www.zefox.net> <aRUJPryA4Vmu8dDD@www.zefox.net> <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org> <87ldkai9lu.fsf@panix.com> <5dd66c4c-ed4d-4034-9fb3-f9079a513595@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On 13.11.2025 10:52, Ronald Klop wrote: > Op 13-11-2025 om 10:07 schreef Carl Shapiro: >> Ronald Klop <ronald@FreeBSD.org> writes: >> >>> My thought was triggered by this as a build of opendjk11 failed with a >>> jemalloc error. >>> https://lists.freebsd.org/archives/freebsd-pkg-fallout/2025- >>> September/804963.html >> >> Is this build failure very reproducible? Is there more of a stack trace >> to go with it? >> >> When the jemalloc witness code observes a locking error the process >> should abort immediately with a SIGABRT. However, there is SIGBUS >> reported in the build output prior to the witness error which makes it >> look like OpenJDK may have been handling a signal while the witness code >> was running. If malloc is somehow being called from a signal handler >> that is asking for trouble. >> >> Here's a closed issue from the old jemalloc repository about a witness >> error when malloc was called from a signal handler >> >> https://github.com/jemalloc/jemalloc/issues/1224 > > > Hi, > > I only have this example. I don't run armv7 myself. > Unfortunately the armv7 pkg builders don't run that often. > > This is the only failure on main-armv7, but AFAIK no new pkg build run > for main-armv7 has happened since. > https://portsfallout.com/fallout? > port=java%2Fopenjdk&maintainer=&env=armv7&category=&flavor= > > I just noticed that the full build log is also already gone from the pkg > build server. > > Regards, > Ronald. I am also a victim of this problem. In my case, unfortunately, the problem is rare and transient. It occurs intermittently and can be resolved by restarting the make. I can confirm that the problem is not related to a specific port. I have experienced it with gdal, qt6-webengine, and rust at minimum. I'm guessing it may be related to memory pressure before OOM. Unfortunately, I'm out of ideas now... Michalhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10c8be48-e9cd-4574-868f-51b113159311>