SEGV in evolution 3.36.3

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

SEGV in evolution 3.36.3

Gnome Evolution - General mailing list
Twice evo has SEGVed on me. ATM the best BT I have is:

 Program terminated with signal SIGSEGV, Segmentation fault.
#0  malloc_consolidate (av=av@entry=0x7fa884000020) at malloc.c:4475
4475 malloc.c: No such file or directory.
[Current thread is 1 (Thread 0x7fa8cd7fe700 (LWP 13122))]
(gdb) bt full
#0  malloc_consolidate (av=av@entry=0x7fa884000020) at malloc.c:4475
        idx = <optimized out>
        fb = 0x7fa884000038
        maxfb = 0x7fa884000078
        p = 0x7fa800000002
        nextp = <optimized out>
        unsorted_bin = 0x7fa884000080
        first_unsorted = <optimized out>
        nextchunk = <optimized out>
        size = <optimized out>
        nextsize = <optimized out>
        prevsize = <optimized out>
        nextinuse = <optimized out>
#1  0x00007fa99c6c3040 in _int_free
    (av=0x7fa884000020, p=0x7fa8844807f0, have_lock=<optimized out>) at malloc.c:4400
        size = 0x11800
        fb = <optimized out>
        nextchunk = 0x7fa884491ff0
        nextsize = 0x50
        nextinuse = <optimized out>
        prevsize = <optimized out>
        bck = <optimized out>
        fwd = <optimized out>
        __PRETTY_FUNCTION__ = "_int_free"
#2  0x00007fa99fb222b6 in magazine_cache_trim
    (allocator=0x7fa99fbd7400 <allocator>, stamp=<optimized out>, ix=<optimized out>)
    at ../glib-2.62.6/glib/gslice.c:678
        chunk = 0x7fa884491e90
        chunk_size = 0xf0
        current = 0x7fa8887fa930
        trash = 0x7fa89c2f6930
        current = <optimized out>
        next = <optimized out>
        prev = <optimized out>
#3  magazine_cache_push_magazine
    (ix=<optimized out>, magazine_chunks=<optimized out>, count=0x6)
    at ../glib-2.62.6/glib/gslice.c:709
        current = <optimized out>
        next = <optimized out>
        prev = <optimized out>
#4  0x00007fa99fb234da in thread_memory_magazine2_unload
    (tmem=0x7fa88c2d1000, ix=<optimized out>) at ../glib-2.62.6/glib/gslice.c:1117
        mag = <optimized out>
--Type <RET> for more, q to quit, c to continue without paging--
        tmem = 0x7fa88c2d1000
        ix = <optimized out>
        chunk_size = 0xf0
        acat = <optimized out>
#5  g_slice_free1 (mem_size=<optimized out>, mem_block=0x7fa96062a0f0)
    at ../glib-2.62.6/glib/gslice.c:1117
        tmem = 0x7fa88c2d1000
        ix = <optimized out>
        chunk_size = 0xf0
        acat = <optimized out>
#6  0x00007fa99fc0eb8f in g_type_free_instance (instance=0x7fa96062a1b0)
    at ../glib-2.62.6/gobject/gtype.c:1946
        node = <optimized out>
        class = 0x7fa9640035d0 [g_type: CamelEwsMessageInfo/CamelMessageInfoBase/CamelMessageInfo]
        allocated = 0x7fa96062a0f0 ""
        private_size = <optimized out>
        ivar_size = <optimized out>
        __FUNCTION__ = "g_type_free_instance"
#7  0x00007fa9a0716445 in camel_folder_summary_remove_uid ()
    at /usr/lib64/libcamel-1.2.so.62
#8  0x00007fa990e984d1 in  () at /usr/lib64/evolution-ews/libcamelews-priv.so
#9  0x00007fa990e9980b in  () at /usr/lib64/evolution-ews/libcamelews-priv.so
#10 0x00007fa990e9a921 in  () at /usr/lib64/evolution-ews/libcamelews-priv.so
#11 0x00007fa9a071e203 in camel_folder_synchronize_sync ()
    at /usr/lib64/libcamel-1.2.so.62
#12 0x00007fa9a076bd20 in  () at /usr/lib64/libcamel-1.2.so.62
#13 0x00007fa99fb2e7a3 in g_thread_pool_thread_proxy (data=<optimized out>)
    at ../glib-2.62.6/glib/gthreadpool.c:308
        task = 0x5563d49075c0
        pool = 0x5563d47afbd0
#14 0x00007fa99fb2e09d in g_thread_proxy (data=0x7fa96033ed40)
    at ../glib-2.62.6/glib/gthread.c:805
        thread = 0x7fa96033ed40
        __FUNCTION__ = "g_thread_proxy"
#15 0x00007fa99c806f30 in start_thread (arg=<optimized out>) at pthread_create.c:479
        ret = <optimized out>
        pd = <optimized out>
        unwind_buf =
              {cancel_jmp_buf = {{jmp_buf = {0x7fa8cd7fe700, 0xd7973861b11cc973, 0x7ffd0ec46d1e, 0x7ffd0ec46d1f, 0x7fa888ad53f0, 0x7fa8cd7fe700, 0x28c6a29e049cc973, 0x28c401616cb0c973}, mask_was_saved = 0x0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0x0}}}
--Type <RET> for more, q to quit, c to continue without paging--
        not_first_call = 0x0
#16 0x00007fa99c73a1bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: SEGV in evolution 3.36.3

Andre Klapper
On Thu, 2020-06-04 at 07:14 +0000, Joakim Tjernlund wrote:
> Twice evo has SEGVed on me

Then please file bug reports in the issue tracker by following
https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines

Thanks,
andre
--
Andre Klapper  |  [hidden email]
https://blogs.gnome.org/aklapper/


_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: SEGV in evolution 3.36.3

Gnome Evolution - General mailing list
In reply to this post by Gnome Evolution - General mailing list
On Thu, 2020-06-04 at 09:14 +0200, Joakim Tjernlund via evolution-list
wrote:
#7  0x00007fa9a0716445 in camel_folder_summary_remove_uid ()
    at /usr/lib64/libcamel-1.2.so.62
#8  0x00007fa990e984d1 in  () at /usr/lib64/evolution-ews/libcamelews-
priv.so
#9  0x00007fa990e9980b in  () at /usr/lib64/evolution-ews/libcamelews-
priv.so
#10 0x00007fa990e9a921 in  () at /usr/lib64/evolution-ews/libcamelews-
priv.so
#11 0x00007fa9a071e203 in camel_folder_synchronize_sync ()
    at /usr/lib64/libcamel-1.2.so.62
#12 0x00007fa9a076bd20 in  () at /usr/lib64/libcamel-1.2.so.62

        Hi,
apart of missing the debuginfo for evolution-data-server and
evolution-ews, it would make more sense to file bugs like this as bugs,
because this is a mailing list for user questions and because it's much
easier to track such things in the bug tracker. I cannot tell where
exactly the problem is, but let's start here:
https://gitlab.gnome.org/GNOME/evolution-ews/issues/new

From the little the backtrace shows, it seems to me that one of your
EWS folders has removed a message on the server and evolution-ews tries
to remove it also from the local cache. Though, it's only a guess.

As a quick workaround (if it's really about it), let evo-ews download
the folder content from scratch by moving away
  ~/.cache/evolution/mail/<ews-account-id>/folders.db
I'd not delete it, in case you'd like to reproduce the crash, thus it
could be returned back. The folder in question, if you've configured
more mail accounts, should have a 'folder-tree' file beside that
folders.db file.
        Bye,
        Milan

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: SEGV in evolution 3.36.3

Gnome Evolution - General mailing list
On Thu, 2020-06-04 at 09:28 +0200, Milan Crha via evolution-list wrote:

>
> On Thu, 2020-06-04 at 09:14 +0200, Joakim Tjernlund via evolution-list
> wrote:
> #7  0x00007fa9a0716445 in camel_folder_summary_remove_uid ()
>     at /usr/lib64/libcamel-1.2.so.62
> #8  0x00007fa990e984d1 in  () at /usr/lib64/evolution-ews/libcamelews-
> priv.so
> #9  0x00007fa990e9980b in  () at /usr/lib64/evolution-ews/libcamelews-
> priv.so
> #10 0x00007fa990e9a921 in  () at /usr/lib64/evolution-ews/libcamelews-
> priv.so
> #11 0x00007fa9a071e203 in camel_folder_synchronize_sync ()
>     at /usr/lib64/libcamel-1.2.so.62
> #12 0x00007fa9a076bd20 in  () at /usr/lib64/libcamel-1.2.so.62
>
>         Hi,
> apart of missing the debuginfo for evolution-data-server and
> evolution-ews, it would make more sense to file bugs like this as bugs,
> because this is a mailing list for user questions and because it's much
> easier to track such things in the bug tracker. I cannot tell where
> exactly the problem is, but let's start here:
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.gnome.org%2FGNOME%2Fevolution-ews%2Fissues%2Fnew&amp;data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7C84baeeaafe34448d158208d80858fc88%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637268525575260836&amp;sdata=Wqu%2FUqu6iiT%2FJHDihLesjdnHQSStHrI3bAOC92gdmGA%3D&amp;reserved=0
>
> From the little the backtrace shows, it seems to me that one of your
> EWS folders has removed a message on the server and evolution-ews tries
> to remove it also from the local cache. Though, it's only a guess.

That would be a correct guess. I often delete lots mail from mail lists and then
move to another folder to some thing else.

>
> As a quick workaround (if it's really about it), let evo-ews download
> the folder content from scratch by moving away
>   ~/.cache/evolution/mail/<ews-account-id>/folders.db
> I'd not delete it, in case you'd like to reproduce the crash, thus it
> could be returned back. The folder in question, if you've configured
> more mail accounts, should have a 'folder-tree' file beside that
> folders.db file.
>         Bye,
>         Milan
>
> _______________________________________________
> evolution-list mailing list
> [hidden email]
> To change your list options or unsubscribe, visit ...
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.gnome.org%2Fmailman%2Flistinfo%2Fevolution-list&amp;data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7C84baeeaafe34448d158208d80858fc88%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637268525575270832&amp;sdata=LfrA85z3lfWg0iQ3jNJsWjyfGSyooD%2B0zfOx8AMAvbI%3D&amp;reserved=0

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list