Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unhandled Exception #98

Closed
HEB2021 opened this issue Apr 17, 2023 · 3 comments
Closed

Unhandled Exception #98

HEB2021 opened this issue Apr 17, 2023 · 3 comments

Comments

@HEB2021
Copy link

HEB2021 commented Apr 17, 2023

WARNING @ retrojsvice.dll C:\build\src\viceplugins\retrojsvice\src\http.cpp:76 -- HTTP response not provided, sending internal server error
PANIC @ retrojsvice.dll C:\build\src\viceplugins\retrojsvice\src\vice_plugin_api.cpp:198: Unhandled exception traversing the vice plugin API: regex_error(error_stack): There was insufficient memory to determine whether the regular expression could match the specified character sequence.
[0418/031602.252:FATAL:common.cpp(109)]

This was the last message the server said before it crashed. The client was IE6 on Win2000 over a 24Kbps Dial up connection I know I cant expect it to be fast over dial up but im very patient. Hopefully this helps you figure something out txt me if you need more info

@ttalvitie
Copy link
Owner

Thank you for the report, and sorry for the late reply. I believe this error is caused by the bad regex implementation in the MSVC C++ standard library combined with the long URLs we get in cases where there is a lot of input events (mouse move/key press) and a very slow connection. I will eventually fix this by reimplementing the URL parsing without regexes or limiting the URL length in the JavaScript code (or both), but it's not a top priority as it shouldn't break browsing with normal usable speeds.

@HEB2021
Copy link
Author

HEB2021 commented May 30, 2023

All good theres no rush for such an edge case exception such as one caused by slow speeds. I have major respect for what youre creating here its made using older devices a lot easier. :))

@ttalvitie
Copy link
Owner

This should be finally fixed in v0.9.10.0. Please open a new issue if the issue continues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants