1.0.4

It seems like #160 accidentally broken import of profiles in some circumstances from Chrome < 69. Before #160, we always took the first profile in the list *but* the profiles were not sorted chronologically. After #160 but before this PR, we were taking the chronologically first.

After this PR, we always take the chronologically last `CpuProfile` event in the trace.

CHANGELOG.md

@@ -1,9 +1,17 @@
 ## Unreleased
 
+## [1.0.4] - 2018-09-12
+
+### Fixed
+
+* Fix import from Chrome < 69 when there are multiple profiles [#161]
+
 ## [1.0.3] - 2018-09-10
 
 ### Fixed
 
+* Fix import for Chrome 69, support leading idle time before first call [#160]
+
 ## [1.0.2] - 2018-09-04
 
 ### Fixed

package.json

@@ -1,6 +1,6 @@
 {
   "name": "speedscope",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "description": "",
   "repository": "jlfwong/speedscope",
   "main": "index.js",

src/import/chrome.ts

@@ -74,7 +74,6 @@ export function importFromChromeTimeline(events: TimelineEvent[]): Profile {
   for (let event of events) {
     if (event.name == 'CpuProfile') {
       cpuProfile = event.args.data.cpuProfile as CPUProfile
-      break
     }
 
     if (event.name == 'Profile') {