Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348311

Summary:

Stack overflow during deleting multiple unmerged branches

Product:

[Technology] EGit

Reporter:

Dariusz Luksza <dariusz.luksza>

Component:

Core

Assignee:

Project Inbox <egit.core-inbox>

Status:

RESOLVED DUPLICATE

QA Contact:

Severity:

major

Priority:

CC:

christian.halstrick, jens.baumgart, matthias.sohn, remy.suen, stepan.stolyarov

Version:

1.0

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
Stack overflow exception	none

Description Dariusz Luksza

2011-06-04 18:03:04 EDT

I want to delete old branches in my local egit repository, some of them was merged into master branch by gerrit. I've selected four or five branches in Delete Branch and click 'OK' then the error dialog appears, the Delete Branch dialog was still there and also selected branches was there, but in fact branches was deleted.

EGit version: 1.0.0.201106032213

This stacktrace was repeated five times with different messages:
* An internal error occurred during: "Decoration Calculation".
* An internal error occurred during: "GitDecoratorJob[/home/lock/workspace/egit/egit/.git]".
* An internal error occurred during: "Repository Change Scanner".
* Error occurred during status handling
* Unhandled event loop exception

Because of BugZilla comment limitation I've used paste bin for publishing full stacktrace:
http://pastebin.com/ATqSmbgr

Comment 1 Dariusz Luksza

2011-06-04 18:21:01 EDT

Created attachment 197349 [details]
Stack overflow exception

Comment 2 Stepan Stolyarov

2011-06-24 06:29:48 EDT

I can confirm this on Windows 7.

Eclipse SDK 3.6.2
EGit feature version: 1.0.0.201106090707-r

This doesn't seem to be related to any particular activity. I have been opening a `git gui` when it happened.

Comment 3 Jens Baumgart

2011-09-30 03:22:22 EDT

*** Bug 359491 has been marked as a duplicate of this bug. ***

Comment 4 Kevin Sawicki

2012-05-10 19:52:40 EDT

I believe this is a duplicate of bug344402

It has the same stacktrace stemming from the GitDocument class

*** This bug has been marked as a duplicate of bug 344402 ***