[ui] "Working..." splash stuck on Span view screen
See original GitHub issueI see this when running UI from the query service i.e. 1.37+
The console error trace looks like:
Uncaught TypeError: Cannot read property 'openChildren' of undefined
(anonymous function) @ trace.js:94
jQuery.extend.each @ jquery.js:365
(anonymous function) @ trace.js:92
jQuery.extend.each @ jquery.js:365
expandSpans @ trace.js:80
filterAdded @ trace.js:74
(anonymous function) @ trace.js:273
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (3 by maintainers)
Top Results From Across the Web
App stuck on Splash Screen - MSDN - Microsoft
i have An issues in my App which working fine iOS but on Android Stuck on Splash Screen it stuck 8 times from...
Read more >UI is stuck in splash Screen in flutter - Stack Overflow
But my UI is stuck in splash screen and my Future.delayed function is not compiling. class Splash_Screen extends StatefulWidget { @override ...
Read more >"Loading UI" splash screen takes a long time, and material ...
stuck at "loading UI" for about 5-10 min sometimes longer. app finally opens and can work like normal. open up preferences, click on...
Read more >Migrate your existing splash screen implementation to Android ...
If you have previously implemented a custom splash screen in Android 11 or lower, you'll need to migrate your app to the SplashScreen...
Read more >IS Suite is stuck on splash screen while executing Launch ...
Reboot run again all good, get the splash screen then launch condition dialog. Run it again and it halts again in the Splash...
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
back to this issue… we do have a bug in the UI, IMHO
a headless trace shouldn’t cause problems. Ex. it can be the case that the root span is missing, but everything else is present. The data here is similar in shape to a headless trace (i.e. the root-most span’s parent is missing)
took me a long time to figure out how to test this 😛 If anyone has better ideas, please comment here https://github.com/openzipkin/zipkin/pull/1089