[jbosstools-issues] [JBoss JIRA] (JBDS-3383) Include Feature Patch for WTP 3.6.3 into JBDS 8.1

[Victor Rubezhny (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052359#comment-13052359 ] 

Victor Rubezhny edited comment on JBDS-3383 at 3/20/15 4:49 PM:
----------------------------------------------------------------

[~maxandersen] 

The following snippet:
{code}
var top = screen.height / 2;
{code}

is the simplest way to get into that infinite loop.For sure, there are other ways in a javascript to get the same result, but even when I saw this issue appearance it was pretty difficult to localize the problem until I've got this simple code that reproduces the issue. And yes, the fix is as easy as add the binding name into the set of names that are already processed. Otherwise, the binding has being constantly added to the bindings to process, so the for cycle at line 630 never ends... at least until the free memory come to the end.

Regarding the producing of WTP v. 3.6.4...  I see no chances to make it possible: there is only one Feature Patch made (this one) after 3.6.3 (SR2) is released. It could be possible in case some other Feature Patches were acquired, but there are not. I don't think it's OK for WTP to release another build just because of one issue. May be I'm too pessimistic, but I don't believe they will agree to produce 3.6.4.


was (Author: vrubezhny):
[~maxandersen] 

The following snippet:
{code}
var top = screen.height / 2;
{code}

is the simplest way to get into that infinite loop.For sure, there are other ways in a javascript to get the same result, but even when I saw this issue appearance it was pretty difficult to localize the problem. And yes, the fix is as easy as add the binding name into the set of names that are already processed. Otherwise, the binding has being constantly added to the bindings to process, so the for cycle at line 630 never ends... at least until the free memory come to the end.

Regarding the producing of WTP v. 3.6.4...  I see no chances to make it possible: there is only one Feature Patch made (this one) after 3.6.3 (SR2) is released. It could be possible in case some other Feature Patches were acquired, but there are not. I don't think it's OK for WTP to release another build just because of one issue. May be I'm too pessimistic, but I don't believe they will agree to produce 3.6.4.

> Include Feature Patch for WTP 3.6.3 into JBDS 8.1
> -------------------------------------------------
>
>                 Key: JBDS-3383
>                 URL: https://issues.jboss.org/browse/JBDS-3383
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: target-platform
>    Affects Versions: 8.1.0.CR1
>            Reporter: Victor Rubezhny
>            Assignee: Nick Boldt
>            Priority: Critical
>             Fix For: 8.1.0.GA
>
>         Attachments: WTP Patches 3.6.3-P.png
>
>
> When the fix for [Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515] was made, the WTP 3.6 stream was already closed (it's ended with 3.6 SR2), so the fix was made only for WTP 3.7 stream.
> JSDT Feature Patch was made due to let the users to bring the fix back to their 3.6 SR2 environments. See: [Bug 461160 - Backport the fix for 'Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160]
> Can we apply this fix into JBDS 8.1? 
> Technically, the Feature Patch installs org.eclipse.wst.jsdt.feature.patch feature that brings fixed org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar instead of org.eclipse.wst.jsdt.core_1.3.300.v201410221502.jar harmed by the bug.
> Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository: http://download.eclipse.org/webtools/repository/luna



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)