This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
This issue was reported manually by alexvsimon. It already has 1 duplicates Build: Oracle Solaris Studio 12.4 (2014/10/03 bc3251f82efb) VM: Java HotSpot(TM) 64-Bit Server VM, 25.25-b02, Java(TM) SE Runtime Environment, 1.8.0_25-b17 OS: SunOS User Comments: GUEST: loading debugger Stacktrace: java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:3181) at java.util.ArrayList.grow(ArrayList.java:261) at java.util.ArrayList.ensureExplicitCapacity(ArrayList.java:235) at java.util.ArrayList.ensureCapacityInternal(ArrayList.java:227) at java.util.ArrayList.add(ArrayList.java:458) at org.tmatesoft.svn.core.internal.util.SVNSkel.appendChild(SVNSkel.java:285)
Created attachment 150869 [details] stacktrace
This looks like SVN problem.
filed to svnkit. In the meantime jut switch to javahl or cli if this really bothers you.
Apparently fixed in SVNKit. Alex, you seem to knowhow to reproduce, maybe you should check and verify it's fixed in the latest SVNKit snapshot.
This is regression between prev and current Studio IDE. So it's regression between NB 7.4 and NB 8.0.1. We have to provide fix to the customer with support contract, so I propose the following: Please, prepare new bundled SVNKit (or/and other nb modules) built on top of 8.0.2 and attach it to the IZ. We would ask sustaining to provide modules for the customer. If customer verifies that regression is gone, then we push it into 8.0.2 Patch 1.
If SVNKit with the fix is not yet available, we need to bundle the last one without regression
(In reply to Vladimir Voskresensky from comment #6) > If SVNKit with the fix is not yet available, we need to bundle the last one > without regression By *we* you clearly mean *you* (as Studio). No way NetBeans goes down back to SVNKit 1.7 (which was bundled along with 7.4 [1]) and completely drop the support for Subversion 1.8 because one of your clients has a corrupted checkout metadata: according to SVNKit evaluation and the fix: > commit 82ffd964d7067d9bbe466063c5943b1f0954bca3 > Author: Dmitry Pavlenko <pavlenko@tmatesoft.com> > Date: Thu Dec 4 21:28:55 2014 +0100 > SVNKIT-569: SVNSkel#parse falled into an infinite loop (causing OOME) if skel format was incorrect (no closing ')' character), now fixed. [1] - http://hg.netbeans.org/releases/annotate/release74/libs.svnClientAdapter.svnkit/external/binaries-list
Created attachment 151260 [details] bundle patch for 8.0.2
Attaching the patched nbm for svnClientAdapter.svnkit. The included svnkit should contain the fix, try to install the nbm and let me know if it helps. If not, attach updated heap dump.
Created attachment 151262 [details] bundled nbm with new svnkit
(In reply to Ondrej Vrabec from comment
(In reply to Ondrej Vrabec from comment #9) > Attaching the patched nbm for svnClientAdapter.svnkit. The included svnkit > should contain the fix, try to install the nbm and let me know if it helps. > If not, attach updated heap dump. Thank you, Ondra. CR_20258172 is updated accordingly. Waiting for the customer verification. Thank you very much again!
(In reply to Ondrej Vrabec from comment #7) > (In reply to Vladimir Voskresensky from comment #6) > > If SVNKit with the fix is not yet available, we need to bundle the last one > > without regression > No way NetBeans goes down back to SVNKit 1.7 (which was bundled along with > 7.4 [1]) and completely drop the support for Subversion 1.8 Sorry for confusion. I meant downgrade to i.e. 1.8.4 if bug was introduced in current 1.8.5. Anyway it doesn't look necessary for now. We'd better wait for any official 1.8.Next with the fix.
(In reply to Vladimir Voskresensky from comment #13) > I meant downgrade to i.e. 1.8.4 if bug was introduced in current 1.8.5. I don't think it would help. The relevant code is there since 2009-04-22 (from svnkit's git blame) so downgrading to any 1.8.x version would make a difference. But they promise to deliver a new stable release soon, so i believe in few weeks we'll be able to upgrade.
(In reply to Ondrej Vrabec from comment #14) > (In reply to Vladimir Voskresensky from comment #13) > > I meant downgrade to i.e. 1.8.4 if bug was introduced in current 1.8.5. > I don't think it would help. The relevant code is there since 2009-04-22 > (from svnkit's git blame) so downgrading to any 1.8.x version would make a > difference. > But they promise to deliver a new stable release soon, so i believe in few > weeks we'll be able to upgrade. This is great. Usually all this official communications with customers takes time, so we have this weeks :-)
Ondra, the OOM fix was included into SVNKit 1.8.7 Could you, please, integrate it? (and into release801 branch as well) Thanks!
upgrading svnkit. If it helps your user, i will either backport to 8.0.1/2 or let you cherry-pick the commit into the branch you're building on. fix: http://hg.netbeans.org/core-main/rev/a4cc3e5c6a81
Integrated into 'main-silver', will be available in build *201501240002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/a4cc3e5c6a81 User: Ondrej Vrabec <ovrabec@netbeans.org> Log: #249094 - OutOfMemoryError: Java heap space Upgrade SVNKit to 1.8.7
Ondra, Could you, please, transplant fix into release801 branch (for upcoming 8.0.2 Patch 1). Thanks! Vladimir.
Did it help? Does the upgrade fix your customer's issue?
... marian, tonda, do you agree with backporting an external library's update to 8.0.2?
(In reply to Ondrej Vrabec from comment #20) > Did it help? Does the upgrade fix your customer's issue? We hope, yes :-)
(In reply to Ondrej Vrabec from comment #21) > ... marian, tonda, do you agree with backporting an external library's > update to 8.0.2? I agree, assuming we can make sure that the upgrade does not break anything for the users. By testing, or at least by judging from the changelogs between 1.8.4 and 1.8.7.
Ondrej pushed new SVNKit on 24th of Jan. Do we have any known bug reports related to this upgrade?
(In reply to Vladimir Voskresensky from comment #24) > Ondrej pushed new SVNKit on 24th of Jan. Do we have any known bug reports > related to this upgrade? No, we don't. Too early to make any conclusion however. But looking at the change logs, it looks mostly as a lot of bugfixes and some performace improvements: http://svn.svnkit.com/repos/svnkit/tags/1.8.7/CHANGES.txt
i will backport to 801 branch on Friday unless there are any objections
http://hg.netbeans.org/releases/rev/cdee1f85275a http://hg.netbeans.org/releases/rev/af790844c0fc
Ondrej, thank you so much!