coredumps
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2.3k
- Forks
- 254
- PR merge metrics
- No merged PRs in 30d
Description
**Current Behavior:**
After updating webkit to 2-42-4 on archlinux (and rebuilding luakit) I'm experiencing instabilities. Two times a SIGSEGV and once a SIGABRT
**Desired Behavior:**
don't crash
**How can we reproduce it (step by step):**
As before, it seems archlinux.org triggers something. I'd need to do some more testing for step-by-step reproduction.
**Environment:**
Linux Distribution & Version:
archlinux, linux 6.6.7.arch1-1
Output of `luakit --version`:
luakit 2.3.3-15-gb143b383
built with: webkit 2.42.4 (installed version: 2.42.4)
GTK 3.24.38
GLIB 2.78.3
SOUP 3.4.4
**Note about webkit issues:**
If you're reporting a rendering issue, please test it with the gnome
browser ephiphany as well. If the issue occurs there too, we're very
likely not able to help. These issues should be reported to webkit:
https://bugs.webkit.org
I don't know how useful backtraces are but there seems to be an issue with malloc? (This is from the SIGABRT coredump)
(gdb) bt
#0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1 0x00007fa4dfefe8a3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2 0x00007fa4dfeae668 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3 0x00007fa4dfe964b8 in __GI_abort () at abort.c:79
#4 0x00007fa4dfe97390 in __libc_message (fmt=fmt@entry=0x7fa4e000e55d "%s\n") at ../sysdeps/posix/libc_fatal.c:150
#5 0x00007fa4dff087b7 in malloc_printerr (str=str@entry=0x7fa4e00117d8 "malloc(): mismatching next->prev_size (unsorted)") at malloc.c:5765
#6 0x00007fa4dff0bd9c in _int_malloc (av=av@entry=0x7fa438000030, bytes=bytes@entry=88) at malloc.c:4076
#7 0x00007fa4dff0ccad in __GI___libc_malloc (bytes=bytes@entry=88) at malloc.c:3329
#8 0x00007fa4e00b4763 in g_malloc (n_bytes=88) at ../glib/glib/gmem.c:130
#9 0x000056105d128605 in ipc_endpoint_new ()
#10 0x000056105d125875 in ()
#11 0x00007fa4e00dda05 in g_thread_proxy (data=0x56105f21ddf0) at ../glib/glib/gthread.c:831
#12 0x00007fa4dfefc9eb in start_thread (arg=) at pthread_create.c:444
#13 0x00007fa4dff807cc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crashes on Arch Linux with WebKit 2.42.4, using the reported gdb backtrace and the ipc_endpoint_new entry point as the first investigation points. Done means the SIGSEGV and SIGABRT no longer occur when exercising the reported archlinux.org case, with a regression check for the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arch-linux, c, linux, lua
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100