From 551b72b0181b042b75f7186782a44653c6420a14 Mon Sep 17 00:00:00 2001 From: Jonne Ransijn Date: Sun, 27 Oct 2024 00:58:31 +0200 Subject: [PATCH] Documentation: Add one more option for getting started Using a profiler is another great way to find issues --- Documentation/GettingStartedContributing.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/GettingStartedContributing.md b/Documentation/GettingStartedContributing.md index 15ea606026e..ac049562cfa 100644 --- a/Documentation/GettingStartedContributing.md +++ b/Documentation/GettingStartedContributing.md @@ -26,6 +26,7 @@ Here are some of the ways you can find an issue in Ladybird: * Manually, by using the browser as you normally would. * By finding failing WPT tests on [WPT.fyi](https://wpt.fyi/results/?label=master&product=ladybird). Note that while fixes are welcome, you don't need to submit issue reports for individual tests. * By finding WPT tests on [WPT.fyi](https://wpt.fyi/results/?label=master&product=ladybird) that are [timing out in Ladybird](https://wpt.fyi/results/?product=ladybird&q=status%3Atimeout). For a real-world walk-through of doing that from start to finish with an actual timing-out-in-Ladybird test case, see the [“Fixing a WPT timeout in Window.postMessage()”](https://www.youtube.com/watch?v=X4S9afzRTXs) “browser hacking” video. +* By using a profiling tool such as [Callgrind](https://valgrind.org/docs/manual/cl-manual.html) to find code that can be improved. If you’re not necessarily already a proficient C++ programmer, beginning by troubleshooting WPT tests may be the very best way to get started contributing to the project — especially if you _do_ already have some proficiency with frontend JavaScript code.