Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.5.0 Beta 1] Client crashes #1229

Closed
ser72 opened this issue Dec 2, 2013 · 13 comments
Closed

[1.5.0 Beta 1] Client crashes #1229

ser72 opened this issue Dec 2, 2013 · 13 comments

Comments

@ser72
Copy link

ser72 commented Dec 2, 2013

Steps
Sync client to ownCloud user
Modify Account to sync same directory to same server with a different user ID
Sync will occur, then client will crash

Problem signature:
Problem Event Name: APPCRASH
Application Name: owncloud.exe
Application Version: 0.0.0.0
Application Timestamp: 52974a4a
Fault Module Name: libneon-27.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5283d92c
Exception Code: c0000005
Exception Offset: 00005c97
OS Version: 6.1.7601.2.1.0.256.49
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

@ogoffart
Copy link
Contributor

ogoffart commented Dec 3, 2013

Hi, looks similair to #1225

We need more information to be able to fix this problem. We need to be able to reproduce the problem. Or have a backtrace or log which would tell us what hapenned.

Thanks

@ser72
Copy link
Author

ser72 commented Dec 3, 2013

@ogoffart This is 100% reproducible via the steps above:

Sync client to ownCloud user
Modify Account to sync same directory to same server with a different user ID
Sync will occur, then client will crash

@ogoffart
Copy link
Contributor

ogoffart commented Dec 3, 2013

I could not reproduce the crash on linux. I ran it with valgrind and i had one warning before the sync which i fixed in csync. (commit 3590db4)

Do you start a clean sync or keep local data?

@ogoffart
Copy link
Contributor

ogoffart commented Dec 3, 2013

I also could not reproduce the problem on Windows 8

@ser72
Copy link
Author

ser72 commented Dec 3, 2013

I was testing on Windows 7. I kept local data

@ser72
Copy link
Author

ser72 commented Dec 3, 2013

@ogoffart Just reproduced on Beta 2. Is there any specific information I can capture?

@ogoffart
Copy link
Contributor

ogoffart commented Dec 4, 2013

Would it be possible to provide a backtrace? Or at least the client log.
(use --logfile filename.log to save the log in a file)

@ser72
Copy link
Author

ser72 commented Dec 4, 2013

@ogoffart Not sure how to get a backtrace -- but client logs are on S3 -- under Support/Client_issue/log_crash.txt

@dragotin
Copy link
Contributor

dragotin commented Dec 5, 2013

I also can not reproduce that, not on Linux and also not on Win7

@ser72 I put a file gdb.zip to Support/Client_issues Can you unzip it on your windows machine and than run the client in the debugger?

You need to change into the gdb directory, and call

.\gdb.exe \program files\owncloud\owncloud.exe

and within gdb:

run --logwindow

Once the client crashes, type where and pass us the output please. Thanks!

@ser72
Copy link
Author

ser72 commented Dec 5, 2013

@dragotin Crash dump is locatred on S3 in Support/Client_issues/crash.txt

@danimo
Copy link
Contributor

danimo commented Dec 5, 2013

@ser72 btw: whenever possible, please put the logs into a gist (https://gist.github.com/) and link them here so everyone can participate in debugging.

@ser72
Copy link
Author

ser72 commented Dec 5, 2013

@dragotin
Copy link
Contributor

dragotin commented Dec 6, 2013

Can be close, @ser72 please retest with the next beta.

@dragotin dragotin closed this as completed Dec 6, 2013
ogoffart added a commit that referenced this issue Jan 13, 2014
This avoids closing it again and possibly crashing

Maybe the cause of the crash described in
#1229
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants