I know if I use octane in laravel it will live in memory even after the request, but it comes with one problem, I need to clear the variables from memory after each request. If I don't it may cause some problems for next user. How can I do it effectively?
Do you know how variable scopes work in PHP? Are you familiar with the concept of garbage collection?
In a normal Laravel application, you wouldn't use global or static variables to store application state, so leaking variables shouldn't be a problem. Singleton services also shouldn't maintain an internal state that could leak between requests.
You can "clear" a variable by setting it to null or calling unset() on it. However, you don't typically need to do this, since the variable is garbage collected once it goes out of scope.
If you can post the code that you're worried about, I can take a look at it to see if it could cause issues.
@foxdevuz Well this is one of things you need to be mindful of when using a shared process for multiple requests like you are with Octane. There isn’t any answer other than, “be mindful of what variables you‘re setting, and clear them between requests.”
Why do you even have a variable persisting its value between HTTP requests? Where is this variable set and used? Because it’s quite hard to assign a variable in Laravel given it’s very heavily OOP-based, so variables tend to be at a class- or method-level rather than global.
