-
-
Notifications
You must be signed in to change notification settings - Fork 882
Logs from opening 15000 swf games #9047
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
Comments
A lot of these are failing with Unknown AVM1 opcode: 137. Also, there's unknown AVM1 opcode 120, which seems to have a several kilobytes of data on it (those take up most of the logs). |
Here are the most common errors:
Additionally, here are some unique errors:
Notice that a lot of errors are just "failed to fetch" or "invalid SWF".
|
I've noticed in my own tests that there are quite a lot of 'Unknown AVM1 opcode: Unknown { opcode:' errors |
All of the |
Looks like the repo is overwhelmed by the number of bug reports, so a recheck is unlikely to be very useful. Also looks that running multiple ruffle instances at once, sometimes crashes some of them with info
|
Oh, I think this specific panic will be (as a lucky coincidence) will be fixed by #15535 that was just merged today! 😅 |
Describe the bug
Recently I created simple fuzzer, that downloaded 30 GB of swf from some sites, and later tried to open them for few seconds.
With its help I collected such output from each game(most not printed anything to console) - res2.txt.zip
Example errors:
Name of file is simplified version of url which full list you can find here - links.txt
Alsa bugs are probably caused by me when restarting gnome-shell which freeze from time to time
I will try once per few months to run fuzzer on my machine to check which of this errors are fixed and which errors are new
Expected behavior
Games should not print any errors if possible
Affected platform
Desktop app
Operating system
Ubuntu 22.10
Browser
No response
Additional information
Ruffle 01.01.2023 nightly
The text was updated successfully, but these errors were encountered: