PX4 / PX4-user_guide

PX4 User Guide

Home Page:https://docs.px4.io/main/en/index.html

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Parameter Reference crashes chrome tab when loaded initially

benjinne opened this issue · comments

When accessing the parameter_reference page from its url or from google, it seems to always initially crashe my chrome tab.
The only way I'm able to access the page is by accessing the root docs page then clicking through the menu to access it.

https://docs.px4.io/main/en/advanced_config/parameter_reference.html

The tab goes unresponsive and I have to close it

image

I've had this issue for a long time and finally got around to posting it. It doesn't seem to matter which version of chrome I'm running and it also happens on mobile

I'm not sure what to suggest - that page works fine for me on Chrome, Firefox and Safari. Tested also a bunch of versions via Browserstack and on my phone.

Is your computer underpowered? This is a big page.

No it's pretty powerful and I have a strong Internet connection. Once the page is loaded it seems to work fine until I close chrome and reopen it. It's weird that if I go through the menu to the parameter reference page it always works, however using the direct link to the page causes issues when a browser has just opened.

Thank you. I'm going to close this because I don't think it is debuggable.

This page is huge and I hope to shrink it soon - actually provide vehicle-specific versions, which each will be smaller. That may well help.

I find myself often searching Google for px4 parameters and using the first link then it inevitably crashes my browser. I then go through the menu to access the parameter page. I can try and provide output from the browser debugger next time it happens

OK, I'll reopen. But this is almost certainly a resource issue or it would affect many other pages.

I'm going to close this because I think it may have been fixed, or will be soon by PX4/PX4-Autopilot#22191

This removed some spurious > chars in the output that browsers were smart enough to ignore, but which could have caused failures. The fixes will go live next time someone modifies a parameter.