[JBoss JIRA] (JBIDE-10881) JBoss Tools JSP Editor is very slow with large selections
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-10881:
---------------------------------------------
Summary: JBoss Tools JSP Editor is very slow with large selections
Key: JBIDE-10881
URL: https://issues.jboss.org/browse/JBIDE-10881
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M5
Reporter: Viacheslav Kabanovich
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
1. Create a JSF KickStart project.
2.Open inputUserName.jsp
3. Copy 1000 times line
{code}
<h1><h:outputText value="#{Message.header}"/></h1>
{code}
4. Select these 1000 lines.
5. Delete and Save.
6. Undo by Ctrl+Z.
Editor freezes for several minutes. Debugger shows that most time is spent for method SelectionBar.updateNodes() called by SelectionBar.notifyChanged.
The problem is that when 1000 lines are removed, XML model sends thousands of deferred events about each removed XML node, so that instead of one call to SelectionBar.updateNodes(), there are thousands of them.
I suggest creating UIJob at the first call to SelectionBar.notifyChanged, and ignoring subsequent calls until the job is not done.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-10905) BrowserSim: null argument exception
by Yahor Radtsevich (JIRA)
Yahor Radtsevich created JBIDE-10905:
----------------------------------------
Summary: BrowserSim: null argument exception
Key: JBIDE-10905
URL: https://issues.jboss.org/browse/JBIDE-10905
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.3.0.Beta1
Reporter: Yahor Radtsevich
Assignee: Yahor Radtsevich
Fix For: 3.3.0.Beta1
*Steps to reproduce:*
# Start Eclipse and close all editors and all views.
# Restart Eclipse.
# Try to run BrowserSim by clicking on its icon on the Eclipse toolbar.
*Actual result:*
Nothing happens, the following stack trace is printed to the console.
{code}
org.eclipse.core.runtime.AssertionFailedException: null argument:
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:290)
at org.jboss.tools.vpe.browsersim.eclipse.util.BrowserSimLauncher.launchBrowserSim(BrowserSimLauncher.java:56)
at org.jboss.tools.vpe.browsersim.eclipse.actions.RunBrowserSimAction.run(RunBrowserSimAction.java:48)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months