Musab Gultekin

Sorry I meant changing middlewares system. Not the queue. I really like the current status of queuing system. So instaed of adding a delay middleware, we'll have a different middleware...

I just made some changes in addition to your code in the queue branch. So I basically added reqPreQueueMiddlewares. And then moved all the middlewares that can cancel the request....

We could add options for `chromedp.NewExecAllocator`. As type of `ExecAllocatorOption`. So anyone can set custom flags for their needs. Or it could be in request options, setted for every request.

Are you connecting the headless browser from outside of the container. Cause you should be inside. Cause according to the chromedp library docs, it should be inside.

Ive just pushed a possible fix. And Ive updated the chromedp library. Can you test again.

How many requests are you making concurrently? If youre on 16gb mem device. You can probably make 100~ Note that, @TheUltimateCookie tries to make 1000 concurrently on the original message....

Oh, Thats weird. Ive just tried on ubuntu and it worked. Are you using BrowserEndpoint and connecting to chromedp/headless-shell docker image?

Hmm, unfortunately I dont even know whats happening here. I would recommend starting headless docker image and using BrowserEndpoint. Btw, i have installed google chrome and not chromium. Idk if...

Oh! I just realised you used req.Rendered = false in your code. That makes the geziyor not use the rendered chrome at all!

Hi! Thanks for reporting that! Its not possible rn. Since actions are hardcoded. Im working on adding a way to add custom actions.