Rosa Gutierrez

@Focus-me34, what version of Solid Queue are you running? And when you say you're removing anything related to Solid Queue, what Active Job adapter are you using instead?

No, that looks good to me re: configuration. You said: > I tried removing all the lines in my code related to solidQueue, and I can confirm that this is...

Hey @rajeevriitm, no, no real solutions. I had an async adapter that would run the supervisor, workers and dispatchers and everything together in the same process, which would save memory....

Hey all, so sorry about this! I've been swamped with other stuff at work, but I'm going to look into this on Monday.

@IvanPakhomov99, @rajeevriitm, could you try downgrading to version v1.1.2 and let me know if the issue persists? Also, what version of Ruby are you using?

@rajeevriitm, I'm afraid I wasn't 😞 I reviewed all code from v1.1.0 and didn't identify anything that could leak memory. This was before @IvanPakhomov99 shared that testing 1.1.0, 1.1.1, 1.1.2,...

Oh! Thanks a lot for confirming that! I had only looked down to version 1.1.0. I'm on-call this week so a bit short on time but will try to figure...

Hey @cjamison, thanks for writing this up! This is all very strange. > This did nothing to the queue database. Maybe because the queue database already existed? No... [it should...

Hey @stefanoc, could you copy your `database.yml` configuration? Is this in development or production? Have you defined `config.solid_queue.connects_to` for the environment you are running this in?

Huh, I just tested a brand new app using Rails 8.0.0.beta1 and everything worked perfectly from the start, just following the instructions and configuring Solid Queue in development, using SQLite...