Can't compile the Performance Advisor report with the following error. Any tips appreciated!
!ENTRY org.eclipse.osgi 4 0 2020-04-09 00:37:49.570!MESSAGE Application error!STACK 1java.lang.AssertionError at com.arm.meerkat.application.capturedata.Frame.<init>(Frame.java:25) at com.arm.meerkat.application.capturedata.FrameProvider.initialiseGaFrames(FrameProvider.java:227) at com.arm.meerkat.application.capturedata.FrameProvider.doInitialise(FrameProvider.java:135) at com.arm.meerkat.application.capturedata.Provider.initialise(Provider.java:65) at com.arm.meerkat.application.capturedata.CaptureData.initialise(CaptureData.java:111) at com.arm.meerkat.application.PerformanceAdvisor.call(PerformanceAdvisor.java:242) at com.arm.meerkat.application.Application.start(Application.java:94) at com.arm.meerkat.application.Application.start(Application.java:1) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:660) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597) at org.eclipse.equinox.launcher.Main.run(Main.java:1468)
Hi Wildman,
Thanks for the bug report - can you share the data file so we can reproduce? Feel free to drop an email to mobilestudio <at> arm <dot> com.
Cheers,Pete
Just sent an email. By repeating captures over and over I managed once to get a working one, but a dozen or so other tries failed with the same error.
Just to log the workaround to help anyone else hitting the same problem:
The issue
The issue occurs when connecting to an application that is already running. We capture frame annotation events for a number of frames with a negative start time relative to the official start of the Streamline capture. These all get clipped to time=0, which results in an assertion for zero length frames.
The workaroundThere are two workarounds:
Thanks for the bug report and helping improve the tool, Pete