Weird behavior Error code: STATUS_BREAKPOINT

The STATUS_BREAKPOINT error in Chrome and Edge typically indicates that there's an issue with the JavaScript code that's causing the browser's debugger to halt execution. This can sometimes be due to a breakpoint set in the developer tools, but since you're experiencing this issue even without the console open, it's likely something else.

Here are a few steps you can take to troubleshoot and hopefully resolve the issue:

1. Check for Infinite Loops or Intensive Tasks: Make sure there are no infinite loops or highly intensive tasks running in your JavaScript code that could be causing the browser to halt.

2. Source Maps: If you're using source maps, there might be an issue with them that's causing the debugger to stop. Try disabling source maps in your build process temporarily to see if the issue persists.

3. Debugging: Since the issue doesn't occur when the console is open, you can try to debug by adding debugger; statements in your code to see if you can catch where the execution stops.

4. Error Handling: Add global error handling in your JavaScript to catch any unhandled exceptions that might be causing the issue. You can do this by adding an event listener for the error event on the window object.

window.addEventListener('error', function(event) {
    console.error('Caught an error:', event.message);
    return false;
});

1. Check for Browser-Specific Code: Since the issue doesn't occur in Firefox, check if there's any browser-specific code that might not be compatible with Chrome or Edge.

2. Update Dependencies: If you're using Vite or other dependencies, make sure they are all up to date. Sometimes, bugs in these tools can cause unexpected behavior in certain browsers.

3. Isolate the Problem: Start by commenting out all your JavaScript and then gradually uncomment sections of it and test until you find the problematic code.

4. Check Network Requests: Look at the network tab in the developer tools to see if there are any failed requests or resources that are not loading correctly.

5. Console Logs: Add console logs throughout your code to trace the execution flow and identify where things might be going wrong.

6. Check for CORS Issues: Cross-Origin Resource Sharing (CORS) issues can sometimes cause scripts to fail. Ensure that your local and production environments are configured correctly to handle CORS.

If none of these steps help, you might want to create a minimal reproducible example and ask for help on forums or consider filing a bug report with the browser vendor if you suspect it's a browser issue.

Remember to remove any debugger; statements and console logs before deploying your application to production.