---- Reported by chaz@yorba.org 2013-08-06 12:34:00 -0700 ----

Original Redmine bug id: 7306
Original URL: http://redmine.yorba.org/issues/7306
Searchable id: yorba-bug-7306
Original author: Charles Lindsay
Original description:

In the conversation-mop-up branch, I got an error due to a null replay_queue
in imap-engine-generic-folder.vala:

    
    
    ** (geary:24040): CRITICAL **: geary_imap_engine_replay_queue_schedule: assertion `GEARY_IMAP_ENGINE_IS_REPLAY_QUEUE (self)' failed
    

Here's the stack trace:

    
    
    #0  g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>, 
        args=args@entry=0x7fff8a911aa8) at /build/buildd/glib2.0-2.36.0/./glib/gmessages.c:981
    #1  0x00007f2096917492 in g_log (log_domain=log_domain@entry=0x0, 
        log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, 
        format=format@entry=0x7f209695c38a "%s: assertion `%s' failed")
        at /build/buildd/glib2.0-2.36.0/./glib/gmessages.c:1010
    #2  0x00007f20969174b9 in g_return_if_fail_warning (log_domain=log_domain@entry=0x0, 
        pretty_function=pretty_function@entry=0x668440 <__PRETTY_FUNCTION__.25566> "geary_imap_engine_replay_queue_schedule", 
        expression=expression@entry=0x6679f8 "GEARY_IMAP_ENGINE_IS_REPLAY_QUEUE (self)")
        at /build/buildd/glib2.0-2.36.0/./glib/gmessages.c:1019
    #3  0x00000000005a6533 in geary_imap_engine_replay_queue_schedule (self=0x0, 
        op=0x7f200c8c16f0)
        at /home/chaz/devel/geary/src/engine/imap-engine/imap-engine-replay-queue.vala:130
    #4  0x0000000000599813 in geary_imap_engine_generic_folder_do_list_email_by_id_async_co (
        _data_=0x1c4a9c0)
        at /home/chaz/devel/geary/src/engine/imap-engine/imap-engine-generic-folder.vala:929
    #5  0x00000000005999ec in geary_imap_engine_generic_folder_do_list_email_by_id_async (
        self=<optimized out>, method=0x1c6ea60 "\300\315@\001", 
        method@entry=0x665ecf "list_email_by_id_async", initial_id=0x0, 
        count=<optimized out>, required_fields=<optimized out>, flags=<optimized out>, 
        accumulator=0x7f2024977da0, cb=cb@entry=0x0, cb_target=cb_target@entry=0x0, 
        cancellable=0x1c6ea60, 
        _callback_=_callback_@entry=0x599ed0 <geary_imap_engine_generic_folder_list_email_by_id_async_ready>, _user_data_=_user_data_@entry=0x17b9c50)
        at /home/chaz/devel/geary/src/engine/imap-engine/imap-engine-generic-folder.vala:7
    #6  0x0000000000599db0 in geary_imap_engine_generic_folder_real_list_email_by_id_async_co
        (_data_=0x17b9c50)
        at /home/chaz/devel/geary/src/engine/imap-engine/imap-engine-generic-folder.vala:888
    #7  0x0000000000502845 in geary_app_conversation_monitor_load_by_id_async_co (
        _data_=0x2fda180)
        at /home/chaz/devel/geary/src/engine/app/app-conversation-monitor.vala:403
    #8  0x0000000000502b3e in geary_app_conversation_monitor_load_by_id_async (
        self=<optimized out>, initial_id=initial_id@entry=0x0, count=<optimized out>, 
        flags=flags@entry=GEARY_FOLDER_LIST_FLAGS_LOCAL_ONLY, cancellable=<optimized out>, 
        _callback_=_callback_@entry=0x5037c0 <geary_app_conversation_monitor_local_load_async_ready>, _user_data_=_user_data_@entry=0x1c4e720)
        at /home/chaz/devel/geary/src/engine/app/app-conversation-monitor.vala:7
    #9  0x00000000005035c8 in geary_app_conversation_monitor_local_load_async_co (
        _data_=0x1c4e720)
        at /home/chaz/devel/geary/src/engine/app/app-conversation-monitor.vala:337
    #10 0x00000000005037be in geary_app_conversation_monitor_local_load_async (
        self=<optimized out>, 
        _callback_=_callback_@entry=0x50c960 <geary_app_local_load_operation_execute_async_ready>, _user_data_=_user_data_@entry=0x7f2027846d50)
        at /home/chaz/devel/geary/src/engine/app/app-conversation-monitor.vala:7
    #11 0x000000000050c8f6 in geary_app_local_load_operation_real_execute_async_co (
        _data_=0x7f2027846d50)
        at /home/chaz/devel/geary/src/engine/app/conversation-monitor/app-local-load-operation.vala:13
    #12 0x00000000005091bd in geary_app_conversation_operation_queue_run_process_async_co (
        _data_=0x1412cc0)
        at /home/chaz/devel/geary/src/engine/app/conversation-monitor/app-conversation-operation-queue.vala:58
    #13 0x00007f2096e831d7 in g_simple_async_result_complete (simple=0x1982400)
        at /build/buildd/glib2.0-2.36.0/./gio/gsimpleasyncresult.c:777
    #14 0x00007f2096e832d9 in complete_in_idle_cb (data=<optimized out>)
        at /build/buildd/glib2.0-2.36.0/./gio/gsimpleasyncresult.c:789
    #15 0x00007f209690ff05 in g_main_dispatch (context=0x1419970)
        at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3054
    #16 g_main_context_dispatch (context=context@entry=0x1419970)
        at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3630
    #17 0x00007f2096910248 in g_main_context_iterate (context=0x1419970, block=block@entry=1, 
        dispatch=dispatch@entry=1, self=<optimized out>)
        at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3701
    #18 0x00007f20969106ba in g_main_loop_run (loop=0x1538690)
        at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3895
    #19 0x00007f20983854a5 in gtk_main () at /build/buildd/gtk+3.0-3.6.4/./gtk/gtkmain.c:1160
    #20 0x00000000005dec74 in yorba_application_run (self=0x1406060, 
        args=args@entry=0x7fff8a911f78, args_length1=args_length1@entry=3)
        at /home/chaz/devel/geary/src/common/common-yorba-application.vala:143
    #21 0x000000000046eaef in _vala_main (args=0x7fff8a911f78, args_length1=3)
        at /home/chaz/devel/geary/src/client/main.vala:10
    #22 0x00007f2095a97ea5 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
    #23 0x000000000045e9c9 in _start ()
    

It looks like what's happening is a close_async for the folder is pending
while we attempt to re-open the folder, presumably using the new account-wide
email operations code. The state gets out of whack with both operations taking
turns on the stack, leaving the object in an invalid state, where the
open_count is nonzero, but the replay_queue is null.

Related issues:
related to geary - 7512: Outlook: UI temporarily stops responding after
move (Open)



---- Additional Comments From geary-maint@gnome.bugs 2013-09-23 18:01:00 -0700 ----

### History

####

#1

Updated by Charles Lindsay 3 months ago

  * **Subject** changed from _error in conversation-mop-up branch due to opening a folder while it's closing_ to _error due to opening a folder while it's closing_

####

#2

Updated by Jim Nelson about 1 month ago

  * **Assignee** set to _Jim Nelson_

There's a possibilty some of the Outlook.com code I've been working on will
solve this problem.

####

#3

Updated by Jim Nelson about 1 month ago

  * **Assignee** deleted (<strike>_Jim Nelson_</strike>)
  * **Target version** changed from _0.4.0_ to _0.5.0_

Some of the work on #7512 was toward fixing this problem, however that's not
going to land in 0.4, so moving to 0.5.



--- Bug imported by chaz@yorba.org 2013-11-21 20:21 UTC  ---

This bug was previously known as _bug_ 7306 at http://redmine.yorba.org/show_bug.cgi?id=7306

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution