search

christian0101 / svnx

Automatically exported from code.google.com/p/svnx
0 stars 0 forks source link

Closing Reopsitory window crashes #37

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Browse a repository for a while
2. Close window by clicking the red button.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
r117
10.5.7

Please provide any additional information below.

09/06/08 23:01:03 [0x0-0x7b07b].com.lachoseinteractive.svnX[936] svnX:
[SvnInterface.m:162] SvnInitialize: toolVersion=1006002 libVersion=1006002
=> hasLib=1 
09/06/08 23:01:13 svnX[936] Type selection took over 1.000 seconds.
Stopping early.... 
09/06/08 23:02:26 svnX[936] *** -[NSCFArray path]: unrecognized selector
sent to instance 0x1750f5d0 
09/06/08 23:02:26 [0x0-0x7b07b].com.lachoseinteractive.svnX[936] svnX:
[SvnInterface.m:162] SvnInitialize: toolVersion=1006002 libVersion=1006002
=> hasLib=1 
09/06/08 23:02:28 ReportCrash[948] Formulating crash report for process
svnX[936] 
09/06/08 23:02:29 ReportCrash[948] Saved crashreport to
/Users/kim/Library/Logs/CrashReporter/svnX_2009-06-08-230226_KIM-MacPro.crash
using uid: 501 gid: 20, euid: 501 egid: 20 
09/06/08 23:02:29 com.apple.launchd[125]
([0x0-0x7b07b].com.lachoseinteractive.svnX[936]) Exited abnormally:
Segmentation fault

Original issue reported on code.google.com by kim.take...@gmail.com on 8 Jun 2009 at 2:09

Attachments:

GoogleCodeExporter commented 8 years ago 
I think this is (basically) the same as issue 27 that I fixed before but 
related to using the svn libs
 - which I didn't address as I never saw a problem until now.

I think the 'closing repository windows' and crash log are misleading & the 
real clue is the
 '[NSCFArray path]: unrecognized selector…'.  Closing a repo window just helps to create memory churn.

How easy is it for you to reproduce this crash?  I still have not been able to.
I have an idea for a fix but I can't test it if I can't make it crash.

Thanks for reporting this.

Original comment by chris...@gmail.com on 10 Jun 2009 at 12:40

GoogleCodeExporter commented 8 years ago 
At the day I had the problem, I had it two or three times, but cannot reproduce 
any more.

I am trying to open a lot of windows, without any problem.

Original comment by kim.take...@gmail.com on 11 Jun 2009 at 7:31

GoogleCodeExporter commented 8 years ago 
I managed to recreate it.
With 'use libs' on.  Open any WC window in tree mode.  Collapse the root of the 
tree.  Refresh.
If it doesn't crash immediately it will shortly.
However, it always logs '… selector not recognized …' immediately.

My idea was correct.  Fixed in r118.

Original comment by chris...@gmail.com on 11 Jun 2009 at 6:04