Crash when doing analysis
See original GitHub issueUsing latest release I did a Windows collection using “Guided Mode”, let it collect info, then did the installation and the let it do post install collection. Then the analysis crashed.
Redoing analysis with same capture crashes again. Not sure if this is helpful enough, but here’s the crash dump:
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: C:\Tools\ASA_win_2.3.274
[12:33:03 INF] Completed Comparing in 00h:00m:03s:083ms.
fail: Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost[111]
Unhandled exception in circuit 'xbUAKet0Brd2KYP2ZlabD6QaapHrbMCrtP26Bi6dZ0g'.
System.AggregateException: One or more errors occurred. (Object reference not set to an instance of an object.) (Object reference not set to an instance of an object.)
---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.CST.AttackSurfaceAnalyzer.Cli.AttackSurfaceAnalyzerClient.<>c__DisplayClass37_0.<CompareRuns>b__0(CompareResult res) in D:\a\1\s\Cli\AttackSurfaceAnalyzerClient.cs:line 1186
at System.Linq.Parallel.ForAllOperator`1.ForAllEnumerator`1.MoveNext(TInput& currentElement, Int32& currentKey)
at System.Linq.Parallel.ForAllSpoolingTask`2.SpoolingWork()
at System.Linq.Parallel.SpoolingTaskBase.Work()
at System.Linq.Parallel.QueryTask.BaseWork(Object unused)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of inner exception stack trace ---
at System.Linq.Parallel.QueryTaskGroupState.QueryEnd(Boolean userInitiatedDispose)
at System.Linq.Parallel.SpoolingTask.SpoolForAll[TInputOutput,TIgnoreKey](QueryTaskGroupState groupState, PartitionedStream`2 partitions, TaskScheduler taskScheduler)
at System.Linq.Parallel.DefaultMergeHelper`2.System.Linq.Parallel.IMergeHelper<TInputOutput>.Execute()
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Crash analysis: Group and filter your crashes
Slice and dice your crash and network data (using groups and filters) to analyze trends leading to the crash. Understand a particular user's...
Read more >Using a Systemic Approach to Crash Analysis
Developing a crash analysis for rural areas can be a challenging task. Traditionally, a crash site analysis approach is employed for most roadways....
Read more >Excel crashing when using Analysis for Office
Hi Allison,. The constant crashes on your Excel may have occurred due to the corrupted analysis add-in. For us to correct this, we...
Read more >Analyzing a crash report | Apple Developer Documentation
Performing a thorough analysis of a crash report and formulating a hypothesis takes time and practice to develop, but is a critical tool...
Read more >Causation analysis of crashes and near crashes using ...
Kinematics and video identified crashes and near crashes from naturalistic driving data. •. 2-stage crash causation analysis used pre-crash scenarios and 4 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Should be fixed in the latest 2.3.277.
https://github.com/microsoft/AttackSurfaceAnalyzer/releases/tag/v2.3.276 is now available with additional logging for this issue.