question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

crashed app in navigator second request

See original GitHub issue

Environment

  • Operating System: Linux
  • Node Version: v18.7.0
  • Nuxt Version: 3.0.0-rc.12
  • Nitro Version: 0.6.0
  • Package Manager: npm@8.15.0
  • Builder: vite
  • User Config: srcDir, modules, compilerOptions, vue, vite, telemetry, algolia, head, auth, css, build, runtimeConfig
  • Runtime Modules: genesis-design-system/nuxt, @nuxtjs/tailwindcss@5.3.5, @nuxtjs/algolia@1.1.4, @nuxtjs-alt/auth@2.0.20, @nuxtjs/device@3.0.0, unplugin-icons/nuxt, @pinia/nuxt@0.4.3, @nuxtjs/i18n@8.0.0-alpha.3
  • Build Modules: -

Reproduction

For some time here, when we start the server, the first request we make through the browser works fine. If we browse the web through the links everything works fine. However, if we reload the same url twice through f5 or through the address bar, the web becomes saturated, and it presents the aspect that I show you.

It seems that everything has to do with those javascript resources that are waiting to be loaded.

image

Any ideas?

Describe the bug

For some time here, when we start the server, the first request we make through the browser works fine. If we browse the web through the links everything works fine. However, if we reload the same url twice through f5 or through the address bar, the web becomes saturated, and it presents the aspect that I show you.

It seems that everything has to do with those javascript resources that are waiting to be loaded.

Any ideas?

Additional context

No response

Logs

No response

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
agracia-foticoscommented, Oct 19, 2022

Would you try adding lodash-es to vite.optimizeDeps.include?

WORKSS!!! Thanks!!!

nuxt.config.ts

vite: { optimizeDeps: { include: [ ‘lodash-es’ ], } },

0reactions
danielroecommented, Oct 19, 2022

Would you try adding lodash-es to vite.optimizeDeps.include?

Read more comments on GitHub >

github_iconTop Results From Across the Web

App crashes while navigating (Android Only) #10290 - GitHub
After upgrading navigation v6 from v5, sometimes app crashing while ... When i hit to the button it should navigates to the second...
Read more >
Flutter - Navigator.pushNamed makes app crash when calling ...
The most probable cause of the crash seems to be isShop boolean value in HomeScreen . Following are the reasons:.
Read more >
Identifying the cause of common crashes - Apple Developer
Overview. You can identify the causes for many app crashes by looking for specific patterns in the crash report and taking specific diagnostic...
Read more >
My App Crashed, Now What? - RayWenderlich.com
Whenever an app that ran from Xcode crashes, the debugger shows you the line that crashed. Sometimes, however, that line won't be meaningful....
Read more >
LinkedIn Sales Navigator Troubleshooting Guide
This error most likely suggests that you need to re-establish a connection with LinkedIn. If possible, go to the Integrations Settings page and ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found