"Multiple problems have occurred" Dialog

When I am debugging and building my project, e2studio slows down the build process (anywhere from 5 to 10 minutes) and then a dialog box is shown:

I then need to restart e2studio, and start over.

This has occurred 3 times within the last 2 hours.

The latest entries from the log file are attached and can be viewed in log.txt.

log.txt

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:17:02.563
!MESSAGE UI freeze of 0.89s at 12:17:01.677
(no stack samples were collected because the monitoring thread starved for CPU)

!ENTRY com.renesas.cdt.debug.adm 4 0 2019-10-21 12:19:24.058
!MESSAGE Failed, getting target status, ADM timed out
!STACK 0
com.renesas.cdt.debug.adm.TargetTimeoutException: target time out on message:'$qrenesas.ITarget:getTargetStatus#a5'
	at com.renesas.cdt.debug.adm.messages.Message.waitForResponse(Message.java:634)
	at com.renesas.cdt.debug.adm.messages.Message.send(Message.java:179)
	at com.renesas.cdt.debug.adm.Target.getStatus(Target.java:20)
	at com.renesas.cdt.debug.adm.Target.pollTarget(Target.java:50)
	at com.renesas.cdt.debug.adm.Target$MonitorTargetThread.run(Target.java:120)
	at java.lang.Thread.run(Unknown Source)

!ENTRY com.renesas.cdt.debug.adm 4 0 2019-10-21 12:21:09.836
!MESSAGE Failed, getting target status, ADM timed out
!STACK 0
com.renesas.cdt.debug.adm.TargetTimeoutException: target time out on message:'$qrenesas.ITarget:getTargetStatus#a5'
	at com.renesas.cdt.debug.adm.messages.Message.waitForResponse(Message.java:634)
	at com.renesas.cdt.debug.adm.messages.Message.send(Message.java:179)
	at com.renesas.cdt.debug.adm.Target.getStatus(Target.java:20)
	at com.renesas.cdt.debug.adm.Target.pollTarget(Target.java:50)
	at com.renesas.cdt.debug.adm.Target$MonitorTargetThread.run(Target.java:120)
	at java.lang.Thread.run(Unknown Source)

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:22:02.219
!MESSAGE UI freeze of 0.54s at 12:22:01.679

!ENTRY com.renesas.cdt.debug.adm 4 0 2019-10-21 12:22:55.876
!MESSAGE Failed, getting target status, ADM timed out
!STACK 0
com.renesas.cdt.debug.adm.TargetTimeoutException: target time out on message:'$qrenesas.ITarget:getTargetStatus#a5'
	at com.renesas.cdt.debug.adm.messages.Message.waitForResponse(Message.java:634)
	at com.renesas.cdt.debug.adm.messages.Message.send(Message.java:179)
	at com.renesas.cdt.debug.adm.Target.getStatus(Target.java:20)
	at com.renesas.cdt.debug.adm.Target.pollTarget(Target.java:50)
	at com.renesas.cdt.debug.adm.Target$MonitorTargetThread.run(Target.java:120)
	at java.lang.Thread.run(Unknown Source)

!ENTRY com.renesas.cdt.debug.adm 4 0 2019-10-21 12:24:43.665
!MESSAGE Failed, getting target status, ADM timed out
!STACK 0
com.renesas.cdt.debug.adm.TargetTimeoutException: target time out on message:'$qrenesas.ITarget:getTargetStatus#a5'
	at com.renesas.cdt.debug.adm.messages.Message.waitForResponse(Message.java:634)
	at com.renesas.cdt.debug.adm.messages.Message.send(Message.java:179)
	at com.renesas.cdt.debug.adm.Target.getStatus(Target.java:20)
	at com.renesas.cdt.debug.adm.Target.pollTarget(Target.java:50)
	at com.renesas.cdt.debug.adm.Target$MonitorTargetThread.run(Target.java:120)
	at java.lang.Thread.run(Unknown Source)

!ENTRY com.renesas.cdt.debug.adm 4 0 2019-10-21 12:26:29.320
!MESSAGE Failed, getting target status, ADM timed out
!STACK 0
com.renesas.cdt.debug.adm.TargetTimeoutException: target time out on message:'$qrenesas.ITarget:getTargetStatus#a5'
	at com.renesas.cdt.debug.adm.messages.Message.waitForResponse(Message.java:634)
	at com.renesas.cdt.debug.adm.messages.Message.send(Message.java:179)
	at com.renesas.cdt.debug.adm.Target.getStatus(Target.java:20)
	at com.renesas.cdt.debug.adm.Target.pollTarget(Target.java:50)
	at com.renesas.cdt.debug.adm.Target$MonitorTargetThread.run(Target.java:120)
	at java.lang.Thread.run(Unknown Source)

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:27:02.816
!MESSAGE UI freeze of 0.60s at 12:27:02.219

!ENTRY com.renesas.cdt.debug.adm 4 0 2019-10-21 12:28:15.845
!MESSAGE Failed, getting target status, ADM timed out
!STACK 0
com.renesas.cdt.debug.adm.TargetTimeoutException: target time out on message:'$qrenesas.ITarget:getTargetStatus#a5'
	at com.renesas.cdt.debug.adm.messages.Message.waitForResponse(Message.java:634)
	at com.renesas.cdt.debug.adm.messages.Message.send(Message.java:179)
	at com.renesas.cdt.debug.adm.Target.getStatus(Target.java:20)
	at com.renesas.cdt.debug.adm.Target.pollTarget(Target.java:50)
	at com.renesas.cdt.debug.adm.Target$MonitorTargetThread.run(Target.java:120)
	at java.lang.Thread.run(Unknown Source)

!ENTRY com.renesas.cdt.debug.adm 4 0 2019-10-21 12:30:01.951
!MESSAGE Failed, getting target status, ADM timed out
!STACK 0
com.renesas.cdt.debug.adm.TargetTimeoutException: target time out on message:'$qrenesas.ITarget:getTargetStatus#a5'
	at com.renesas.cdt.debug.adm.messages.Message.waitForResponse(Message.java:634)
	at com.renesas.cdt.debug.adm.messages.Message.send(Message.java:179)
	at com.renesas.cdt.debug.adm.Target.getStatus(Target.java:20)
	at com.renesas.cdt.debug.adm.Target.pollTarget(Target.java:50)
	at com.renesas.cdt.debug.adm.Target$MonitorTargetThread.run(Target.java:120)
	at java.lang.Thread.run(Unknown Source)

!ENTRY org.eclipse.core.jobs 4 2 2019-10-21 12:30:32.514
!MESSAGE An internal error occurred during: "Win32 refresh daemon".
!STACK 0
java.lang.OutOfMemoryError: Java heap space
	at java.io.WinNTFileSystem.list(Native Method)
	at java.io.File.list(Unknown Source)
	at org.eclipse.core.internal.filesystem.local.LocalFile.childNames(LocalFile.java:101)
	at org.eclipse.core.filesystem.provider.FileStore.childStores(FileStore.java:110)
	at org.eclipse.core.filesystem.provider.FileStore.childInfos(FileStore.java:93)
	at org.eclipse.core.internal.localstore.UnifiedTree.getLocalList(UnifiedTree.java:348)
	at org.eclipse.core.internal.localstore.UnifiedTree.addChildren(UnifiedTree.java:140)
	at org.eclipse.core.internal.localstore.UnifiedTree.addNodeChildrenToQueue(UnifiedTree.java:246)
	at org.eclipse.core.internal.localstore.UnifiedTree.accept(UnifiedTree.java:112)
	at org.eclipse.core.internal.localstore.FileSystemResourceManager.isSynchronized(FileSystemResourceManager.java:742)
	at org.eclipse.core.internal.resources.Resource.isSynchronized(Resource.java:1446)
	at org.eclipse.core.internal.resources.refresh.win32.Win32Monitor$Handle.postRefreshRequest(Win32Monitor.java:209)
	at org.eclipse.core.internal.resources.refresh.win32.Win32Monitor$ResourceHandle.handleNotification(Win32Monitor.java:303)
	at org.eclipse.core.internal.resources.refresh.win32.Win32Monitor.waitForNotification(Win32Monitor.java:601)
	at org.eclipse.core.internal.resources.refresh.win32.Win32Monitor.run(Win32Monitor.java:519)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.eclipse.core.jobs 4 2 2019-10-21 12:30:32.515
!MESSAGE An internal error occurred during: "Building Workspace".
!STACK 0
java.lang.OutOfMemoryError: Java heap space
	at java.util.Arrays.copyOfRange(Unknown Source)
	at java.lang.String.<init>(Unknown Source)
	at java.lang.StringBuilder.toString(Unknown Source)
	at com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.getNodeValueString(Unknown Source)
	at com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.getNodeValueString(Unknown Source)
	at com.sun.org.apache.xerces.internal.dom.DeferredTextImpl.synchronizeData(Unknown Source)
	at com.sun.org.apache.xerces.internal.dom.CharacterDataImpl.getNodeValue(Unknown Source)
	at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.beginNode(Unknown Source)
	at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(Unknown Source)
	at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(Unknown Source)
	at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(Unknown Source)
	at javax.xml.validation.Validator.validate(Unknown Source)
	at com.renesas.cdt.synergy.packs.model.ModuleUtils.parseDocument(ModuleUtils.java:445)
	at com.renesas.cdt.synergy.packs.model.ModuleUtils.parseDocument(ModuleUtils.java:423)
	at com.renesas.cdt.synergy.packs.model.ModuleUtils.parseModuleDescription(ModuleUtils.java:414)
	at com.renesas.cdt.synergy.packs.model.ModuleUtils.parseModuleDescriptionFile(ModuleUtils.java:214)
	at com.renesas.cdt.synergy.packs.model.ModuleUtils.getPossibleModuleDescriptionDocument(ModuleUtils.java:388)
	at com.renesas.cdt.synergy.packs.model.ModuleUtils.getModulesListForAvailableModulesEvent(ModuleUtils.java:344)
	at com.renesas.cdt.synergy.packs.model.ModuleUtils.saveAvailableComponentsSetting(ModuleUtils.java:245)
	at com.renesas.cdt.synergy.contentgen.builder.SynergyProjectBuilder.generateContent(SynergyProjectBuilder.java:106)
	at com.renesas.cdt.synergy.contentgen.builder.SynergyBuilder.incrementalBuild(SynergyBuilder.java:83)
	at com.renesas.cdt.synergy.contentgen.builder.SynergyBuilder.build(SynergyBuilder.java:48)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
	at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:487)

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:30:34.032
!MESSAGE UI freeze of 0.52s at 12:30:33.513

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:30:42.602
!MESSAGE UI freeze of 0.54s at 12:30:42.066
(no stack samples were collected because the monitoring thread starved for CPU)

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:30:43.467
!MESSAGE UI freeze of 0.56s at 12:30:42.905

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:30:45.886
!MESSAGE UI freeze of 0.58s at 12:30:45.309

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:30:47.482
!MESSAGE UI freeze of 0.55s at 12:30:46.936

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:30:48.872
!MESSAGE UI freeze of 0.59s at 12:30:48.277

!ENTRY org.eclipse.ui.monitoring 2 0 2019-10-21 12:30:51.197
!MESSAGE UI freeze of 0.51s at 12:30:50.687

!ENTRY org.eclipse.jface 4 0 2019-10-21 12:30:51.256
!MESSAGE Unhandled event loop exception during blocked modal context.
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?))
	at org.eclipse.swt.SWT.error(SWT.java:4533)
	at org.eclipse.swt.SWT.error(SWT.java:4448)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3819)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:165)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:369)
	at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:481)
	at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:242)
	at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.disconnectFromWorkspace(IDEWorkbenchAdvisor.java:463)
	at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.postShutdown(IDEWorkbenchAdvisor.java:309)
	at org.eclipse.ui.internal.Workbench.shutdown(Workbench.java:3111)
	at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1200)
	at org.eclipse.ui.internal.Workbench.access$22(Workbench.java:1112)
	at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1453)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.Workbench.close(Workbench.java:1450)
	at org.eclipse.ui.internal.WorkbenchConfigurer.emergencyClose(WorkbenchConfigurer.java:147)
	at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.closeWorkbench(IDEWorkbenchErrorHandler.java:244)
	at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handleException(IDEWorkbenchErrorHandler.java:146)
	at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.access$0(IDEWorkbenchErrorHandler.java:137)
	at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler$1.runInUIThread(IDEWorkbenchErrorHandler.java:112)
	at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3819)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
Caused by: java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)
	at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1687)
	at com.renesas.cdt.debug.eventpoints.views.EventpointsView$21.run(EventpointsView.java:1209)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
	... 45 more

!ENTRY org.eclipse.jface 4 0 2019-10-21 12:30:51.258
!MESSAGE Unhandled event loop exception during blocked modal context.
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?))
	at org.eclipse.swt.SWT.error(SWT.java:4533)
	at org.eclipse.swt.SWT.error(SWT.java:4448)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3819)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:165)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:369)
	at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:481)
	at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:242)
	at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.disconnectFromWorkspace(IDEWorkbenchAdvisor.java:463)
	at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.postShutdown(IDEWorkbenchAdvisor.java:309)
	at org.eclipse.ui.internal.Workbench.shutdown(Workbench.java:3111)
	at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1200)
	at org.eclipse.ui.internal.Workbench.access$22(Workbench.java:1112)
	at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1453)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.Workbench.close(Workbench.java:1450)
	at org.eclipse.ui.internal.WorkbenchConfigurer.emergencyClose(WorkbenchConfigurer.java:147)
	at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.closeWorkbench(IDEWorkbenchErrorHandler.java:244)
	at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handleException(IDEWorkbenchErrorHandler.java:146)
	at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.access$0(IDEWorkbenchErrorHandler.java:137)
	at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler$1.runInUIThread(IDEWorkbenchErrorHandler.java:112)
	at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3819)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
Caused by: java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)
	at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1687)
	at com.renesas.cdt.debug.eventpoints.views.EventpointsView$22.run(EventpointsView.java:1263)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
	... 45 more

!ENTRY org.eclipse.core.resources 2 10035 2019-10-21 12:30:53.171
!MESSAGE The workspace will exit with unsaved changes in this session.

!ENTRY org.eclipse.core.jobs 4 2 2019-10-21 12:30:53.187
!MESSAGE An internal error occurred during: "Update SVN Cache".
!STACK 0
java.lang.NullPointerException
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2250)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
	at org.eclipse.team.svn.core.utility.ProgressMonitorUtility$1.run(ProgressMonitorUtility.java:58)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.eclipse.core.jobs 2 2 2019-10-21 12:30:53.622
!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.cdt.dsf.gdb.internal.ui.console.GdbBasicCliConsole$InputReadJob

Why is this happening?  Is there any way I can optimize/configure the IDE to not take a significant performance hit when debugging and building?

  • Hi JasonP-
    Can you provide a bit more information? What version of e2 studio and SSP are you using? What version of Windows?

    Can you provide a screen shot of the modules you are using or a short list of them.

    In my experience PC memory size (or lack of it) can impact compile times and can give a Java error similar to what you are seeing. How much RAM do you have available? If your project is very large, it can be impacted by a small amount of PC memory.

    Does everything work fine for a small project?

    Warren
  • In reply to WarrenM:

    Hi Warren,

    Thanks for your quick response. I will answer your questions in order:
    The version of e2studio and SSP are in the tags of the post: e2studio 6.2.1 and SSP 1.5.3

    Windows 10 Enterprise, 48 GB RAM, Intel core i7-6700HQ

    By "modules" do you mean Synergy Config > Components? If so, the following items have check boxes:
    s5d9_pk
    s5d9 device 1.5.3 (R7FS5D97E3A01CFC)
    s5d9 device 1.5.3 (bsp for s5d9)
    ssp 1.5.3
    ssp_common 1.5.3
    fx 1.5.3
    tx 1.5.3
    ux 1.5.3
    ux_device_class_cdc_acm 1.5.3
    ux_host_class_storage 1.5.3
    sf_console 1.5.3
    sf_el_ux 1.5.3
    sf_el_ux_comms_v2 1.5.3
    sf_wifi_esp_wroom_32 1.5.3
    sf_wifi_esp_wroom_32_onchip_stack 1.5.3
    sf_wifi_esp_wroom_32_socket 1.5.3
    r_adc 1.5.3
    r_cgc 1.5.3
    r_dac 1.5.3
    r_dtc 1.5.3
    r_elc 1.5.3
    r_fmi 1.5.3
    r_gpt 1.5.3
    r_ioport 1.5.3
    r_qspi 1.5.3
    r_sci_i2c 1.5.3
    r_sci_uart 1.5.3
    BlinkyThreadX 1.5.3

    What is a "small project" defined as? Code space? Less modules?
  • In reply to JasonP:

    Hi JasonP-
    Thanx for the additional information. Good idea to put the tools in the tags! It's an uncommon, but helpful practice.

    I guess by small I mean something smaller than your project- in terms of complexity- to see if there is something going on with memory- a leak or not enough Java memory, etc.

    If you close out of other Windows applications, and run your project does the compile go any faster? Do you still see the same error?
  • In reply to WarrenM:

    WarrenM,

    I have not tried a smaller project.

    When I close the other windows applications, the build time does not go any faster. The error still occurs, yes.
  • In reply to JasonP:

    Hi JasonP-
    Ok, I will need to get some help to dig into the details of this issue. Give me a couple of hours to find an expert...
  • In reply to JasonP:

    JasonP,

    Do you have any inspect variables set to Real-time refresh?
    What about Memory windows, etc. for Real-time refresh?

    If so, try either turning off these updates and see if the problem still exists. Once we know that perhaps we can target the issue.
  • In reply to Michael Quirk:

    Hi,

    Do you have anti-virus software installed? The SSP consists of many small files (especially if any Express Logic middleware source is added) which are read by the compiler during a build. If each access has to go through a virus scanner then it may impact performance. Can you try disabling the virus scanner and see if that improves the build time?

    Regards,

    Ian.
  • In reply to Michael Quirk:

    I am not using any Real-time refresh variables, or Expressions. I do have those windows open, but I should be able to use the features with the current hardware without any issues.
    I am also using the Live Trace Console window, but even without the Live Trace Console running the same java heap space error occurs.
  • In reply to Ian:

    Anti-virus is installed, and I understand that it will impact performance. I am not able to disable the anti-virus.

    Would this also impact the "java heap space" error?
  • In reply to JasonP:

    I just attempted to build, without debugging, and received another popup error that forced me to restart.

  • In reply to WarrenM:

    Any updates on this?
  • In reply to JasonP:

    JasonP,

    What version of Java is currently on your machine?
    You can see this by using the command line:
    C:\java -version
    For example this is the version I currently have installed
    java version "1.8.0_211"
    Java(TM) SE Runtime Environment (build 1.8.0_211-b12)
    Java HotSpot(TM) Client VM (build 25.211-b12, mixed mode)

    Suggestion:
    1) backup your project(s).
    2) Download and install the version 7 e2 studio (suggest to a different directory)
    3) Install your SSP 1.5.3 to the version 7 tool.
    4) Import your project(s) and try again.
  • In reply to Michael Quirk:

    e2studio is shipped with a version of java in the installation, and will use this internal version of java by default.

    e.g. in eclipse/e2studio.ini :-

    -vm
    features/com.renesas.jre.win32.win32.x86_1.8.0.181/jre/bin
  • In reply to Michael Quirk:

    Java:

    I would rather not have to install another version of e2studio, as I already have 6 installed.

  • In reply to JasonP:

    Any update on this?

    e2studio does not even start for me now.  When I click the icon, nothing appears: no splash screen, no error/message box etc.

    I have also downloaded and installed the latest e2studio v7.5.1 and the same thing happens: does not start, no splash screen, no error etc.

    Java version:

    I have also tried modifying both eclipse.ini files to point to the java versions that came with the IDEs:

    -vm
    features/com.renesas.jre.win32.win32.x86_1.8.0.65/jre/bin

    and forcing to the version installed:

    -vm

    C:\Program Files (x86)\Java\jre1.8.0_231\bin\javaw.exe

     

    Is there a log file or something that I can post here that will allow for a quick resolution?