Sync Client V1.2.3 Crashes Repetitively #498
Comments
|
last few lines from owncloud log: |
|
memory dump available if required (~ 80 MB) |
|
I think you try to sync directories into a probably read only Shared. Just mentioning, of course we should not crash anyway.... |
|
The "Shared" is full access, but I assume, windows explorer might have an open handle some times on the folder. |
|
Can you please try with http://download.owncloud.org/download/nightly/owncloud-1.2.3-nightly20130404-setup.exe? |
|
Hi Danimo, Protokollname: Application |
|
these are the last lines of the log: |
|
I have put up a GDB for windows at http://download.owncloud.com/download/gdb-win32.zip. Could you unzip it and drag |
|
What @jochenwezel describes is a different crash from what was found&fixed in nightly. Two strange things:
Thanks for you help & patience. |
|
the shared BW_80_BW_138 is read-only for me, yes, that's true!
not really - but it seems to be so...maybe it has been modified by opening it (MS Office might do so sometimes?)
Because the default owncloud sync folder targets to clientsync on the server, I've created an additional sync for the server's Shared folder to get all that stuff. I named it "owncloud Shared" --> yes, the space in the name is correct! :-) |
|
@jochenwezel cool, thanks for the "space" explanation, that clearifies. Now digging for the crash.... |
|
@jochenwezel I fail to reproduce a crash, whatever I do in the sharing, with the latest nightly build. Could you verify again that the crash above really happened with the latest nightly and not 1.2.3? Thanks... |
|
first debug output was from 04.04.2013 18:34 second debug in following is from 05.04.2013 01:03 |
|
@jochenwezel At the chance of sounding annoying: Is that with the nighly build that Klaas posted above? If it is, can you try to move away your .csync_journal file (do not delete it!) and see if after the rebuild the crash still happens? |
|
okay - I see: in last post was something with my hardcopy tool - I stopped it now and tried again; here the output of the new EXE with compile date 05.04.2013 01:03 |
|
@jochenwezel I still can not reproduce. Can you describe what you do that results in the crash? And, I see you work with 4..5.7? Is it possible to reproduce with 5.0.3 as well? |
I just wait for a few seconds (or 2 minutes) until it crashes- that's all. No other activity.
yes, that's correct. We haven't moved to v5 since there had been several upgrade issues with files and Umlauts...
I can't give a timeline for this, yet. But probably in next weeks there is a chance for it... |
|
Hey, that seems similar to what one of our users experiences. Most users are fine, but his client just sits there waiting to sync (x seconds have passed). And as soon as it tries (usually after a few minutes), it freezes for a second or two and windows reports Owncloud stopped functioning. We're using server 5.0.0 with the infinite loop sharing patch (that is part of the v5 branch now, I gather), sync client 1.2.1. When the client with fix for #438 is out, I'll upgrade, but I suspect this is a different crash. I still have on my todo list to gather data about this bug. The PC in question is a Windows 7 64 bit machine. It is different to all other users in that he is the only one with a Samsung series 9 laptop, whereas the rest has Asus and Acer (all very similar models). However, the software (office, MS security essentials, owncloud, windows firewall) used is much the same. |
|
For me it looks like a memory corruption. Could someone get a valgrind or similar log? |
|
Debugged with Valgrind on Linux, trying to sync against a read only share with Server 4.5.8. Valgrind does not report problems. |
|
@jochenwezel can you try with a new nightly build: http://download.owncloud.com/download/nightly/owncloud-1.2.3-nightly20130408-setup.exe Even if it does not crash, I'd appreciate a full log of one sync run, maybe as downloadable zip from somewhere. Thanks! |
|
@dragotin I dropped all stuff from my Shared sync (sync-db plus files) and restarted with nightly from 2013-04-08. IT HASN'T CRASHED ANY MORE!! :-D What ever happened in the last 4 days, it seems that a fix has been added successfully. :-) Here is a full log of a sync run (available till 2013-04-20 at the lastest before deletion): Now, I'm experiencing often "Undefined error situations" (German output in Info dialog: "Undefinierter Fehler-Zustand.") After a few seconds again, it tells me: "Die letzte Synchronisation war erfolgreich." Both messages switch several times (in 1 minute). In parallel, the main status window of owncloud switches between "Verifying connection..." and "Connected with XY as ABC" (all output messages again translated from German by me) |
|
|
|
The undefined error I reported in #513. But about the crash, I don't think it should be necessary to remove the user data, from the user's perspective. And it's kind of unfortunate that we now lost a workstation on which this crash is reproducible. Me getting the required logs and back traces is kind of hard, because it's not my PC and I hard have access to it; the user needs it. But, I'll do my best. |
|
I received two notifications from "a-schild", but I don't see them here. What happened? |
|
@halfgaar me too, see, even github has bugs ;-| |
|
Can you even remove comments? They did seem unrelated to this, so perhaps that's what's happened. |
|
Sorry for the "spam", I did see the same unknown error occured message in the client, |
|
well, I don't know if the same situation of a-schild applies to me - but don't know how to verify. On the other hand, I hope that no corrupt databsae has been created already after the very first sync (it took me 7-8 GB of data transfer volume to get my whole stuff again ;-) |
|
I have been running the one of the nightly builds from last week and have experienced another crash here is the windows event log that was generated from the crash: Name of misapplication: owncloud.exe, Version: 0.0.0.0, time stamp: 0x5162b76f This took place on a patched and up to date Windows 7 system |
|
@bboule Please attach a gdb as explain in #498 (comment) and post the backtrace. |
|
ownCloud 1.2.4 nightly 20130414 Program received signal SIGSEGV, Segmentation fault. |
|
ownCloud 1.2.4 from .com site running on Windows 7 64 bit OC 4.5.8 |
|
@bboule looks worthless unfortunately. Can you describe what you did to have it crash? |
|
@bboule you can create a backtrace of all threads (which we need) using the two commands in the gdb window: would you mind to retry? Thanks. |
|
@bboule and if possible, do not grab the screen, but do an actual copy&paste from the cmd window (the output will be longer than one screen page). |
|
I think my crash was different. I was finally able to test it on the computer in question and generate a stack trace. However, because it was in owncloud_rmdir, I suspect it was part of owncloud/core#2462. |
|
@halfgaar Your crash has been fixed with 1.2.4 (and ownCloud 5.0.4, I hope you have upgraded in the meanwhile). |
|
I've got another crash: Unfortunately I wasn't able to debug with gdb.exe because it's not listed in the dialog when you click on button for debugging. The app crashed when I didn't work with it (just normally running in background). This is the content from VS2012 output window: |
server environment:
owncloud V4.5.7, Ubuntu Linux
client environment:
Win 2008 R2 Server German x64
with latest patches, Kaspersky anti-virus
Win32 exception from event viewer:
----SNIP----
Protokollname: Application
Quelle: Application Error
Datum: 02.04.2013 16:29:35
Ereignis-ID: 1000
Aufgabenkategorie:(100)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: wks23.lan.compumaster.de
Beschreibung:
Name der fehlerhaften Anwendung: owncloud.exe, Version: 0.0.0.0, Zeitstempel: 0x515ade05
Name des fehlerhaften Moduls: msvcrt.dll, Version: 7.0.7601.17744, Zeitstempel: 0x4eeaf722
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000143f9
ID des fehlerhaften Prozesses: 0x6700
Startzeit der fehlerhaften Anwendung: 0x01ce2fae689be272
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\ownCloud\owncloud.exe
Pfad des fehlerhaften Moduls: C:\Windows\syswow64\msvcrt.dll
Berichtskennung: bda21b35-9ba1-11e2-afb7-001cc03d4aa2
Ereignis-XML:
1000
2
100
0x80000000000000
721673
Application
wks23.lan.compumaster.de
owncloud.exe
0.0.0.0
515ade05
msvcrt.dll
7.0.7601.17744
4eeaf722
c0000005
000143f9
6700
01ce2fae689be272
C:\Program Files (x86)\ownCloud\owncloud.exe
C:\Windows\syswow64\msvcrt.dll
bda21b35-9ba1-11e2-afb7-001cc03d4aa2
----SNIP----
----SNIP----
Protokollname: Application
Quelle: Windows Error Reporting
Datum: 02.04.2013 16:29:39
Ereignis-ID: 1001
Aufgabenkategorie:Keine
Ebene: Informationen
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: wks23.lan.compumaster.de
Beschreibung:
Fehlerbucket 3504683365, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Problemsignatur:
P1: owncloud.exe
P2: 0.0.0.0
P3: 515ade05
P4: msvcrt.dll
P5: 7.0.7601.17744
P6: 4eeaf722
P7: c0000005
P8: 000143f9
P9:
P10:
Angefügte Dateien:
C:\Users\wezel\AppData\Local\Temp\WEREA36.tmp.WERInternalMetadata.xml
Diese Dateien befinden sich möglicherweise hier:
C:\Users\wezel\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_owncloud.exe_c07d71cc01b3233b975c27272af3cba49f26c7_296ef53e
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: bda21b35-9ba1-11e2-afb7-001cc03d4aa2
Berichtstatus: 0
Ereignis-XML:
1001
4
0
0x80000000000000
721674
Application
wks23.lan.compumaster.de
3504683365
1
APPCRASH
Nicht verfügbar
0
owncloud.exe
0.0.0.0
515ade05
msvcrt.dll
7.0.7601.17744
4eeaf722
c0000005
000143f9
C:\Users\wezel\AppData\Local\Temp\WEREA36.tmp.WERInternalMetadata.xml
C:\Users\wezel\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_owncloud.exe_c07d71cc01b3233b975c27272af3cba49f26c7_296ef53e
0
bda21b35-9ba1-11e2-afb7-001cc03d4aa2
0
----SNIP----
C:\Users\wezel\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_owncloud.exe_c07d71cc01b3233b975c27272af3cba49f26c7_296ef53e\Report.wer
----SNIP----
Version=1
EventType=APPCRASH
EventTime=130093865761034043
ReportType=2
Consent=1
UploadTime=130093865763684308
ReportIdentifier=bda21b36-9ba1-11e2-afb7-001cc03d4aa2
IntegratorReportIdentifier=bda21b35-9ba1-11e2-afb7-001cc03d4aa2
WOW64=1
Response.BucketId=3504683365
Response.BucketTable=1
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=owncloud.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=0.0.0.0
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=515ade05
Sig[3].Name=Fehlermodulname
Sig[3].Value=msvcrt.dll
Sig[4].Name=Fehlermodulversion
Sig[4].Value=7.0.7601.17744
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=4eeaf722
Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000005
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=000143f9
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=6.1.7601.2.1.0.274.10
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Program Files (x86)\ownCloud\owncloud.exe
UI[3]=owncloud.exe funktioniert nicht mehr
UI[4]=Windows kann online nach einer Lösung für das Problem suchen.
UI[5]=Online nach einer Lösung suchen und das Programm schließen
UI[6]=Später online nach einer Lösung suchen und das Programm schließen
UI[7]=Programm schließen
LoadedModule[0]=C:\Program Files (x86)\ownCloud\owncloud.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Program Files (x86)\ownCloud\QtCore4.dll
LoadedModule[5]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[11]=C:\Windows\syswow64\ole32.dll
LoadedModule[12]=C:\Windows\syswow64\GDI32.dll
LoadedModule[13]=C:\Windows\syswow64\USER32.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[17]=C:\Windows\syswow64\NSI.dll
LoadedModule[18]=C:\Program Files (x86)\ownCloud\zlib1.dll
LoadedModule[19]=C:\Program Files (x86)\ownCloud\libgcc_s_sjlj-1.dll
LoadedModule[20]=C:\Program Files (x86)\ownCloud\libstdc++-6.dll
LoadedModule[21]=C:\Program Files (x86)\ownCloud\QtGui4.dll
LoadedModule[22]=C:\Windows\syswow64\COMDLG32.DLL
LoadedModule[23]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[24]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[25]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[26]=C:\Windows\syswow64\IMM32.DLL
LoadedModule[27]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[28]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[29]=C:\Program Files (x86)\ownCloud\libpng15-15.dll
LoadedModule[30]=C:\Windows\system32\WINMM.DLL
LoadedModule[31]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[32]=C:\Program Files (x86)\ownCloud\QtNetwork4.dll
LoadedModule[33]=C:\Program Files (x86)\ownCloud\QtXml4.dll
LoadedModule[34]=C:\Program Files (x86)\ownCloud\libowncloudsync.dll
LoadedModule[35]=C:\Program Files (x86)\ownCloud\libqtkeychain.dll
LoadedModule[36]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[37]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[38]=C:\Program Files (x86)\ownCloud\libocsync.dll
LoadedModule[39]=C:\Program Files (x86)\ownCloud\libdl.dll
LoadedModule[40]=C:\Program Files (x86)\ownCloud\libiniparser.dll
LoadedModule[41]=C:\Program Files (x86)\ownCloud\libsqlite3-0.dll
LoadedModule[42]=C:\Program Files (x86)\Sizer\sizer.dll
LoadedModule[43]=R:\Admin\Netlogon\Run\Hardcopy_v2011-11-01\HcDLL2_31_Win32.dll
LoadedModule[44]=C:\Windows\system32\uxtheme.dll
LoadedModule[45]=C:\Windows\system32\dwmapi.dll
LoadedModule[46]=C:\Windows\system32\userenv.dll
LoadedModule[47]=C:\Windows\system32\profapi.dll
LoadedModule[48]=C:\Program Files (x86)\ownCloud\libssl-10.dll
LoadedModule[49]=C:\Program Files (x86)\ownCloud\libcrypto-10.dll
LoadedModule[50]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[51]=C:\Windows\system32\rsaenh.dll
LoadedModule[52]=C:\Windows\system32\winhttp.dll
LoadedModule[53]=C:\Windows\system32\webio.dll
LoadedModule[54]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[55]=C:\Windows\system32\WINNSI.DLL
LoadedModule[56]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[57]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[58]=C:\Windows\system32\credssp.dll
LoadedModule[59]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[60]=C:\Windows\system32\mswsock.dll
LoadedModule[61]=C:\Windows\System32\wshtcpip.dll
LoadedModule[62]=C:\Windows\System32\wship6.dll
LoadedModule[63]=C:\Windows\system32\DNSAPI.dll
LoadedModule[64]=C:\Windows\system32\rasadhlp.dll
LoadedModule[65]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[66]=C:\Windows\SysWOW64\msv1_0.DLL
LoadedModule[67]=C:\Windows\system32\cryptdll.dll
LoadedModule[68]=C:\Windows\system32\NLAapi.dll
LoadedModule[69]=C:\Windows\system32\napinsp.dll
LoadedModule[70]=C:\Windows\System32\winrnr.dll
LoadedModule[71]=C:\Program Files (x86)\ownCloud\modules\ocsync_owncloud.dll
LoadedModule[72]=C:\Program Files (x86)\ownCloud\libneon-27.dll
LoadedModule[73]=C:\Program Files (x86)\ownCloud\libintl-8.dll
LoadedModule[74]=C:\Program Files (x86)\ownCloud\libproxy.dll
LoadedModule[75]=C:\Program Files (x86)\ownCloud\libmodman.dll
LoadedModule[76]=C:\Program Files (x86)\ownCloud\libxml2-2.dll
LoadedModule[77]=C:\Windows\system32\security.dll
LoadedModule[78]=C:\Windows\system32\SECUR32.DLL
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Nicht mehr funktionsfähig
ConsentKey=APPCRASH
AppName=owncloud.exe
AppPath=C:\Program Files (x86)\ownCloud\owncloud.exe
----SNIP----
The text was updated successfully, but these errors were encountered: