Agis Anastasopoulos
Agis Anastasopoulos
I'm not a fan of conventional commits, so I wouldn't like to suggest it in this style guide.
Heads up: we've been using this today and everything seems fine.
Note that we were using an in-house, native version of the "format" bundle - no containers involved. Most of the time was spent in gems being loaded by bundler (ie....
Seeing the same issue. Did you get to the bottom of this?
@wjordan Hey, have you been using this patch in production with Ruby 2.5? Have you noticed any performance benefits with it? Thanks!
> Would we expect memory usage to go up? Probably not, running this with a manual GC.compact does seem to keep the memory usage down, but not plateau, so there...
> > That said, if the class objects are never cleared as you demonstrated and are never garbage collected (which they aren't), isn't it expected for the memory to be...
I see your point. However, using a simple script, it seems that Ruby _does_ the right thing and garbage collects classes after you remove their respective constants (and therefore they...
@ljharb For example, the backtrace displayed on the browser is something along the lines of: ``` "ReferenceError: idontexist is not defined", "at new SampleComponent (ssr.bundle.js:35348:5)", "at processChild (ssr.bundle.js:34431:14)", "at resolve...
@conf @dmitry Uninstall every gem that throws this error and re-run `$ gem pristine --all` and then `$ bundle`.