Dominik Woźniak comments

Results 12 comments of


                                            Dominik Woźniak

`findHostInstance_DEPRECATED is deprecated` and `findNodeHandle is deprecated` errors when using `Animated.View` inside `react-native-gesture-handler`'s `GestureDetector`

Hey @winghouchan @LeandroRibeiroo , did you find a workaround? Looks like my app with `@gorhom/bottom-sheet` has stopped working properly

`findHostInstance_DEPRECATED is deprecated` and `findNodeHandle is deprecated` errors when using `Animated.View` inside `react-native-gesture-handler`'s `GestureDetector`

@winghouchan thanks! I did a react-native downgrade to 0.76 as a workaround

Possible memory leak with next.js standalone build

Hey @edodusi thanks for the quick reply! I will try to prepare a repo. I have a suspicion that caching layer connection is the problem but let's wait for confirmation....

Possible memory leak with next.js standalone build

hi @edodusi , I have prepared a repository that allows you to reproduce the test scenario - https://github.com/dominikwozniak/next-standalone-storyblok In the README you will find instructions.You can follow the steps to...

Possible memory leak with next.js standalone build

Regarding debugging, you can also try adding it to the next config file: ```ts experimental: { middlewarePrefetch: "strict", webpackMemoryOptimizations: true, }, webpack: (config, { isServer }) => { // Add...

Possible memory leak with next.js standalone build

Hi @edodusi , do you have any progress?

Possible memory leak with next.js standalone build

Hi @edodusi thanks for your update! 🙏 Yes, I think the `cv` doesn't matter much here. I understand your effort and really appreciate it. I wasn’t able to investigate further...

Possible memory leak with next.js standalone build

@edodusi I haven’t really tried, to be honest. We assume that content from Storyblok should always be visible to the user, so there’s no rate limiting or caching layer -...

Possible memory leak with next.js standalone build

@edodusi thanks will try it out! I'm surprised that, the memory usage stays at a set level and doesn't drop - which would be normal for rate limiting. I'm not...

Possible memory leak with next.js standalone build

Hey @edodusi ! I managed to get back to this topic in the meantime. As you noticed, memory consumption slowly decreases after the spike. This used to be a problem...