After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 752556 - Crash with `free(): invalid next size (fast)`
Crash with `free(): invalid next size (fast)`
Status: RESOLVED DUPLICATE of bug 746195
Product: gjs
Classification: Bindings
Component: general
1.43.x
Other Linux
: Normal normal
: ---
Assigned To: gjs-maint
gjs-maint
Depends on:
Blocks:
 
 
Reported: 2015-07-18 07:50 UTC by Paul Menzel
Modified: 2015-10-30 16:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
GDB-Output of `t a a bt f` and `info registers` (19.14 KB, text/plain)
2015-07-18 07:50 UTC, Paul Menzel 		Details

Description Paul Menzel 2015-07-18 07:50:24 UTC 
Created attachment 307652 [details]
GDB-Output of `t a a bt f` and `info registers`

Using Debian Sid/unstable with the package gjs 1.43.3-2, using the GNOME DE for a long time, there seems to be a crash in `/usr/bin/gjs-console`.

Thanks to corekeeper, the core dump file was saved and loading it in GDB shows the message below.

    Core was generated by `/usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const Main = imports.m'.

Unfortunately there doesn’t seem to be a package with debug symbols for `/usr/bin/gjs-console` available in Debian Sid/unstable. The backtrace is below.

(gdb) bt

+ Trace 235281

  • #0 __kernel_vsyscall
  • #1 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 56
  • #2 __GI_abort
    at abort.c line 89
  • #3 __libc_message
    at ../sysdeps/posix/libc_fatal.c line 175
  • #4 malloc_printerr
  • #5 _int_free
    at malloc.c line 3840
  • #6 sqlite3VdbeMemGrow
    at sqlite3.c line 63239
  • #7 vdbeMemAddTerminator
    at sqlite3.c line 63334
  • #8 valueToText
    at sqlite3.c line 63353
  • #9 valueToText
    at sqlite3.c line 64113
  • #10 likeFunc
    at sqlite3.c line 97228
  • #11 sqlite3VdbeExec
    at sqlite3.c line 72436
  • #12 sqlite3_step
    at sqlite3.c line 69488
  • #13 sqlite3_step
    at sqlite3.c line 4018
  • #14 db_cursor_iter_next
    at tracker-db-interface-sqlite.c line 890
  • #15 db_cursor_iter_next
    at tracker-db-interface-sqlite.c line 2124
  • #16 tracker_db_cursor_iter_next_thread
    at tracker-db-interface-sqlite.c line 1913
  • #17 run_in_thread
    at /build/glib2.0-dCKQ11/glib2.0-2.44.1/./gio/gsimpleasyncresult.c line 858
  • #18 io_job_thread
    at /build/glib2.0-dCKQ11/glib2.0-2.44.1/./gio/gioscheduler.c line 85
  • #19 g_task_thread_pool_thread
    at /build/glib2.0-dCKQ11/glib2.0-2.44.1/./gio/gtask.c line 1231
  • #20 g_thread_pool_thread_proxy
    at /build/glib2.0-dCKQ11/glib2.0-2.44.1/./glib/gthreadpool.c line 307
  • #21 g_thread_proxy
    at /build/glib2.0-dCKQ11/glib2.0-2.44.1/./glib/gthread.c line 764
  • #22 start_thread
    at pthread_create.c line 309
  • #23 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 129 

Please find the output of `t a a bt f` and `info registers` attached.
Comment 1 Cosimo Cecchi 2015-10-27 21:42:19 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 755560 ***
Comment 2 Debarshi Ray 2015-10-30 16:18:24 UTC 

*** This bug has been marked as a duplicate of bug 746195 ***