Pidgin crashes with an Access Violation after a few minutes of operation after logging in

Help
2014-06-19
2014-07-02
  • Joel Pearson
    Joel Pearson
    2014-06-19

    If I open pidgin and wait about 1 minute it crashes everytime.

    I tried to install 1.18.2.0 of sipe, but Norton thinks it's a virus and since I'm on a corporate network I can't make it ignore it.

    Error occured on Thursday, June 19, 2014 at 14:29:31.
    
    Windows Version 6.1 Build 7601 Service Pack 1
    
    C:\Program Files (x86)\Pidgin\pidgin.exe caused an Access Violation at location 665f870f in module C:\Program Files (x86)\Pidgin\plugins\libsipe.dll Reading from location 00000183.
    
    Registers:
    eax=6663d515 ebx=055dead8 ecx=7efdd000 edx=0000006b esi=665f86f0 edi=686591d8
    eip=665f870f esp=0028ecd0 ebp=0028edd8 iopl=0         nv up ei pl nz na pe nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00210202
    
    Call stack:
             C:\Program Files (x86)\Pidgin\plugins\libsipe.dll [1.18.1.0]
    665F870F C:\Program Files (x86)\Pidgin\plugins\libsipe.dll
             C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll [2.28.8.0]
    685EB167 C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_context_dispatch
    685EB90D C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_context_dispatch
    685EBD9D C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_loop_run
             C:\Program Files (x86)\Pidgin\Gtk\bin\libgtk-win32-2.0-0.dll [2.16.6.0]
    022B4260 C:\Program Files (x86)\Pidgin\Gtk\bin\libgtk-win32-2.0-0.dll  gtk_main
    
     
  • Joel Pearson
    Joel Pearson
    2014-06-19

    Managed to upgrade to 1.18.2.0

    didn't help

    Error occured on Thursday, June 19, 2014 at 15:15:40.
    
    Windows Version 6.1 Build 7601 Service Pack 1
    
    C:\Program Files (x86)\Pidgin\pidgin.exe caused an Access Violation at location 5c06871f in module C:\Program Files (x86)\Pidgin\plugins\libsipe.dll Reading from location 00000175.
    
    Registers:
    eax=5c0ad535 ebx=0568bfe8 ecx=7efdd000 edx=0000005d esi=5c068700 edi=686591d8
    eip=5c06871f esp=0028ecd0 ebp=0028edd8 iopl=0         nv up ei pl nz na po nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00210206
    
    Call stack:
             C:\Program Files (x86)\Pidgin\plugins\libsipe.dll [1.18.2.0]
    5C06871F C:\Program Files (x86)\Pidgin\plugins\libsipe.dll
             C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll [2.28.8.0]
    685EB167 C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_context_dispatch
    685EB90D C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_context_dispatch
    685EBD9D C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_loop_run
             C:\Program Files (x86)\Pidgin\Gtk\bin\libgtk-win32-2.0-0.dll [2.16.6.0]
    02194260 C:\Program Files (x86)\Pidgin\Gtk\bin\libgtk-win32-2.0-0.dll  gtk_main
    

    Here is a snapshot from the debug logs just as it crashed:

    (06:15:40) sipe: sipe_core_schedule_execute: executing <+keepalive-timeout>
    (06:15:40) sipe: sipe_core_schedule_execute timeouts count 7 after removal
    (06:15:40) sipe: sipe_schedule_allocate timeouts count 8 after addition
    (06:15:40) sipe: scheduling action <+keepalive-timeout> timeout 239 seconds
    (06:15:40) sipe: sipe_core_schedule_execute: executing <+update-calendar>
    (06:15:40) sipe: sipe_core_schedule_execute timeouts count 7 after removal
    (06:15:40) sipe: sipe_core_update_calendar: started.
    (06:15:40) sipe: sipe_ews_update_calendar: started.
    (06:15:40) sipe: sipe_ews_autodiscover_url: trying 'https://Autodiscover.mycompany.com/Autodiscover/Autodiscover.xml'
    (06:15:40) sipe: sipe_http_parse_uri: host 'Autodiscover.mycompany.com' port 443 path 'Autodiscover/Autodiscover.xml'
    (06:15:40) sipe: sipe_http_transport_new: new autodiscover.mycompany.com:443
    (06:15:40) sipe: transport_connect - hostname: autodiscover.mycompany.com port: 443
    (06:15:40) sipe: using SSL
    (06:15:40) dnsquery: Performing DNS lookup for autodiscover.mycompany.com
    (06:15:40) sipe: sipe_domino_update_calendar: started.
    (06:15:40) sipe: Could not open reg key 'HKCU' subkey 'Software\Lotus\Notes\8.0'.
    Message: (2) The system cannot find the file specified.
    
    (06:15:40) sipe: Could not open reg key 'HKCU' subkey 'Software\Lotus\Notes\7.0'.
    Message: (2) The system cannot find the file specified.
    
    (06:15:40) sipe: Could not open reg key 'HKCU' subkey 'Software\Lotus\Notes\6.0'.
    Message: (2) The system cannot find the file specified.
    
    (06:15:40) sipe: Could not open reg key 'HKCU' subkey 'Software\Lotus\Notes\5.0'.
    Message: (2) The system cannot find the file specified.
    
    (06:15:40) sipe: sipe_domino_update_calendar: notes.ini path:
    
    (06:15:40) sipe: sipe_domino_update_calendar: Domino URI hasn't been discovered, neither provided, disabling.
    (06:15:40) sipe: sipe_domino_update_calendar: disabled, exiting.
    (06:15:40) sipe: sipe_schedule_allocate timeouts count 8 after addition
    (06:15:40) sipe: scheduling action <+update-calendar> timeout 1800 seconds
    (06:15:40) sipe: sipe_core_update_calendar: finished.
    (06:15:40) dnsquery: Error resolving autodiscover.mycompany.com: 11001
    (06:15:40) proxy: Connection attempt failed: Error resolving autodiscover.mycompany.com: 11001
    (06:15:40) sipe: sipe_http_transport_drop: dropping connection 'autodiscover.mycompany.com:443': SSL Connection Failed
    (06:15:40) sipe: sipe_http_transport_free: destroying connection 'autodiscover.mycompany.com:443'
    (06:15:40) sipe: sipe_ews_autodiscover_redirect: trying 'http://Autodiscover.mycompany.com/Autodiscover/Autodiscover.xml'
    (06:15:40) sipe: sipe_http_parse_uri: host 'Autodiscover.mycompany.com' port 80 path 'Autodiscover/Autodiscover.xml'
    (06:15:40) sipe: sipe_http_transport_new: new autodiscover.mycompany.com:80
    (06:15:40) sipe: transport_connect - hostname: autodiscover.mycompany.com port: 80
    (06:15:40) sipe: using TCP
    (06:15:40) dnsquery: Performing DNS lookup for autodiscover.mycompany.com
    (06:15:40) sipe: transport_deferred_destroy: 06D9CB08
    (06:15:40) dnsquery: Error resolving autodiscover.mycompany.com: 11001
    (06:15:40) proxy: Connection attempt failed: Error resolving autodiscover.mycompany.com: 11001
    (06:15:40) sipe: sipe_http_transport_drop: dropping connection 'autodiscover.mycompany.com:80': Could not connect
    (06:15:40) sipe: sipe_http_transport_free: destroying connection 'autodiscover.mycompany.com:80'
    (06:15:40) sipe: sipe_ews_autodiscover_url: trying 'http://Autodiscover.mycompany.com/Autodiscover/Autodiscover.xml'
    (06:15:40) sipe: sipe_http_parse_uri: host 'Autodiscover.mycompany.com' port 80 path 'Autodiscover/Autodiscover.xml'
    (06:15:40) sipe: sipe_http_transport_new: re-establishing autodiscover.mycompany.com:80
    (06:15:40) sipe: transport_connect - hostname: autodiscover.mycompany.com port: 80
    (06:15:40) sipe: using TCP
    (06:15:40) dnsquery: Performing DNS lookup for autodiscover.mycompany.com
    (06:15:40) sipe: sipe_ews_autodiscover_url: trying 'https://mycompany.com/Autodiscover/Autodiscover.xml'
    (06:15:40) sipe: sipe_http_parse_uri: host 'mycompany.com' port 443 path 'Autodiscover/Autodiscover.xml'
    (06:15:40) sipe: sipe_http_transport_new: new mycompany.com:443
    (06:15:40) sipe: transport_connect - hostname: mycompany.com port: 443
    (06:15:40) sipe: using SSL
    (06:15:40) dnsquery: Performing DNS lookup for mycompany.com
    (06:15:40) sipe: transport_deferred_destroy: 06D9CB58
    (06:15:40) dnsquery: Error resolving autodiscover.mycompany.com: 11001
    (06:15:40) proxy: Connection attempt failed: Error resolving autodiscover.mycompany.com: 11001
    Segmentation fault
    
     
  • Stefan Becker
    Stefan Becker
    2014-06-19

    The debug log is not providing enough information. You'll need to provide a debugger backtrace which shows the full call stack with parameters.

    If you can't do that then your only option is to disable publishing calendar information in the account setting and then hope your account will never be upgraded to Lync 2013 with UCS...

     
  • Peter Fyffe
    Peter Fyffe
    2014-06-23

    Hi Stefan,

    I have what appears to be the same problem with version 1.18.2.0 running Windows 7. I posted the debug to the forum about two weeks ago and have not seen a response. I have the pidgin.rpt file, but I do not want to post it to the public forum. Can I email it to you?

    Thanks,

    Peter

     
    • Stefan Becker
      Stefan Becker
      2014-06-23

      Sorry, but I can't find your post with the debug ouput. Can you provide the URL?

      I don't know what a ".rpt" file is. so I don't know if it is helpful or not.

      I need the --debug output from Pidgin and a stack backtrace from the debugger at the point of the crash. In worse case you may have to recompile SIPE without optimization (-O0), because otherwise the stack backtrace might be unusable.

       
  • Stefan Becker
    Stefan Becker
    2014-06-28

    FYI: I have created [bugs:#257] from the provided information. Anybody who can provide better information about this crash please enter it in the bug report.

     

    Related

    Bugs: #257

  • Stefan Becker
    Stefan Becker
    2014-06-28

    I have identified the root cause and verified that with git HEAD the issue is fixed. Details can be found in [bugs:#257]

     

    Related

    Bugs: #257

  • Stefan Becker
    Stefan Becker
    2014-06-29

    For the future: please mention that you upgraded from 1.18.0 (or older) to 1.18.1 (or newer) and then you start to see a crash. That would have made it clear that it was a regression.

     
  • Peter Fyffe
    Peter Fyffe
    2014-07-01

    I installed the patch yesterday and it appears to be working great! Thanks very much.

     
    • Cagri Arslan
      Cagri Arslan
      2014-07-02

      And now i can use 1.18.x.x.

      Thank you Peter.