[StackOverflow/go] selenium/Edge driver fills up memory in golang application

### ROOT CAUSE The issue arises from improper resource management of the Selenium Edge driver in the Go application. The driver instances are not being properly closed, leading to memory leaks. This can happen due to: - **Deferred cleanup**: The `driver.Quit()` method is not called, leaving browser instances open. - **Multiple concurrent instances**: Tests or functions create multiple driver instances without reusing or cleaning up properly. - **Edge-specific issues**: The Edge driver might have memory management inefficiencies compared to other browsers. ### CODE FIX Ensure the driver is properly closed using `defer driver.Quit()` in the same scope as its creation. Example: ```go // Correct usage with deferred cleanup func test() { // Initialize the Edge driver caps := selenium.Capabilities{"browserName": "MicrosoftEdge"} driver, err := selenium.NewRemote(caps, "http://localhost:4444/wd/hub") if err != nil { panic(err) } defer driver.Quit() // Automatically closes the driver when the function exits // Test logic using driver... // driver.Quit() is called here automatically } ``` **Key Fixes**: 1. **Always defer `driver.Quit()`**: Ensure the driver is closed immediately after use. 2. **Avoid nested driver scopes**: Don’t create drivers inside loops or nested functions unless explicitly designed to handle cleanup. 3. **Check for driver leaks**: Use tools like `pprof` to detect unclosed drivers. If the problem persists, check for: - **Edge driver version compatibility** with Selenium. - **Memory profiling** to identify if the issue is driver-specific.