Closed olleharstedt closed 9 years ago
This is another example of a run-time issue. It's not out of scope of a "dports issue" per se, but in practical terms, it is. There's not enough manpower to chase down run time issue on 22,000 ports, especially a report such as this that provides practically zero information (what video? is there a trace? is there a core dump? etc, etc)
Any Youtube video. Easy to reproduce. Firefox is not any port, I'd say.
I can't chase this down. If you have a solution or at least identify the problem, feel free to reopen.
Also at least one new version of firefox has been released since.
Will upgrade and try again, maybe it's fixed. Thanks for your time.
If it is still doing it, try to find someone to help you diagnose it. I simply do not have the time for runtime errors, other people need to contribute to fix port errors like this.
Release 4.