v2.0 release immediately crashes when trying to connect to a repo

102 views
Skip to first unread message

Andrew Metcalf

unread,
Apr 24, 2017, 1:12:06 PM4/24/17
to svnX
I'm trying to connect to a repo via svn+ssh.  I can successfully connect using a different computer still running v1.3.4 of svnX, and I've tried using the same setting on this computer with v2 release.  When I double-click to open the repo, the app immediately crashes.

In case any of the error report might help:

Crashed Thread:        1  Dispatch queue: NSOperationQueue 0x60800042acc0 :: NSOperation 0x608000666240 (QOS: USER_INTERACTIVE)

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0:
--> 
    __TEXT                 0000000100000000-00000001001cd000 [ 1844K] r-x/rwx SM=COW  /Applications/svnX.app/Contents/MacOS/svnX


Thread 1 Crashed:: Dispatch queue: NSOperationQueue 0x60800042acc0 :: NSOperation 0x608000666240 (QOS: USER_INTERACTIVE)
0   app.svnx.two                   0x000000010005a194 0x100000000 + 369044
1   app.svnx.two                   0x000000010005bf76 0x100000000 + 376694
2   app.svnx.two                   0x000000010005c339 0x100000000 + 377657
3   app.svnx.two                   0x0000000100059b5b 0x100000000 + 367451
4   com.apple.Foundation           0x00007fffbeb31644 -[__NSOperationInternal _start:] + 672
5   com.apple.Foundation           0x00007fffbeb2d4fb __NSOQSchedule_f + 201
6   libdispatch.dylib             0x00007fffd282c8fc _dispatch_client_callout + 8
7   libdispatch.dylib             0x00007fffd28429a0 _dispatch_queue_serial_drain + 896
8   libdispatch.dylib             0x00007fffd2835306 _dispatch_queue_invoke + 1046
9   libdispatch.dylib             0x00007fffd282e6b5 _dispatch_root_queue_drain + 476
10  libdispatch.dylib             0x00007fffd282e48c _dispatch_worker_thread3 + 99
11  libsystem_pthread.dylib       0x00007fffd2a7b616 _pthread_wqthread + 1299
12  libsystem_pthread.dylib       0x00007fffd2a7b0f1 start_wqthread + 13



I am using the latest version of Mac OS X.

chris

unread,
Apr 24, 2017, 1:58:28 PM4/24/17
to svnX
Hello Andrew,


On Monday, 24 April 2017 18:12:06 UTC+1, Andrew Metcalf wrote:
I'm trying to connect to a repo via svn+ssh.  I can successfully connect using a different computer still running v1.3.4 of svnX, and I've tried using the same setting on this computer with v2 release.  When I double-click to open the repo, the app immediately crashes.

It looks like your repository cache may be corrupt.
In the Bookmarks window select the repo, click ⚙ (bottom left) & choose Purge Cache of “…”.
Alternatively you can simply delete the file ~/Library/Caches/app.svnx.two/<your-repo’s-UUID>.A.db before launching svnX.

Did that fix it?

CHRIS


Andrew Metcalf

unread,
Apr 24, 2017, 2:08:50 PM4/24/17
to svnX
Yes that seemed to fix it.  I'm not sure how it would have gotten corrupt, I haven't been try anything too advanced.

I do get another error when trying to browse the folders at the bottom of the repository window:  "No handlers could be found for logger". I think this might be an error with the svn server though and not with the app.

 Thanks!

chris

unread,
Apr 24, 2017, 3:05:57 PM4/24/17
to svnX


On Monday, 24 April 2017 19:08:50 UTC+1, Andrew Metcalf wrote:
Yes that seemed to fix it.

Good.  [Being part of the matrix, the numbers in your crash log told me it would. :-)]

 
 I'm not sure how it would have gotten corrupt, I haven't been try anything too advanced.

I’m not sure either.  The cache DBs are supposed to be ACID.  These corruptions happen so infrequently (and may not be noticed until long after) so I have not been able to reproduce anything.

 
I do get another error when trying to browse the folders at the bottom of the repository window:  "No handlers could be found for logger". I think this might be an error with the svn server though and not with the app.

That’s not an svnX error.  I don’t think it’s a Subversion error either.  It may be related to your ssh server/setup.  Google says Python.

 
 Thanks!

You’re welcome.

CHRIS


Reply all
Reply to author
Forward
0 new messages