My Browser Builds (Part 5)

[NotHereToPlayGames]

If you ***REALLY*** want your video playback looked into, it's kind of ON YOU to do some LEGWORK in NARROWING IT DOWN.

*Shoot the messenger* all you want.  But that really is the reality of the situation.

We (you!) need to tell roytam "playback WORKS in this month-day-year release, but it is BROKEN one week later with the month-day+7-year release".

[Goodwin]

21 hours ago, NotHereToPlayGames said:

video playback

I'm not a developer. If roytam1 is a professional, he should look for the causes of the bug and the browser version himself, not send users who do not understand many technical issues to do it.
It would be very funny if when reporting a bug in firefox, mozilla would say "you look for the problem yourself, we don't know anything".

[NotHereToPlayGames]

<del, nwi>

Edited 16 hours ago by NotHereToPlayGames

[NotHereToPlayGames]

<del, nwi>

Edited 16 hours ago by NotHereToPlayGames

[roytam1]

11 hours ago, Goodwin said:

I'm not a developer. If roytam1 is a professional, he should look for the causes of the bug and the browser version himself, not send users who do not understand many technical issues to do it.
It would be very funny if when reporting a bug in firefox, mozilla would say "you look for the problem yourself, we don't know anything".

Those builds are originally for my private use and they are released because of my goodwill that I think they may help others.

This bug doesn't affect me and so I don't have big intention on hunting and fixing it.

If you want this to be fixed you at least need to find when the problem started to occur.

and last but not least, stop gaslighting.

Edited 12 hours ago by roytam1

[Nicholas McAnespy]

@Goodwin @roytam1 I'm not a professional, I just compile Mozilla based browsers for my personal use and hope for the best. For instance, I'm trying to compile Firefox 13+ with Windows 2000 compatibility. One thing that sometimes (but not always) causes runtime execution failure is clicking on tools -> options -> applications which can cause an error in MSVCR71.DLL. Also, after reverting the commit that broke Windows 2000 compatibility, I had a minor problem that is caused by opening a new tab, and the message displayed on the new tab page was relating to an invalid address. That annoyance was caused by the commit for Mozilla bug 728429, which mandated ASLR on Windows. In order to find that, I had to cherry-pick a range of commits between the one that broke Windows 2000 compatibility, and the one mandating ASLR, then compile the source code a few times to narrow down my search. The point is, if a problem does not exist in one of roytam1's browser builds, then exists on a later browser version, the right thing to do is find out what the last good version, and the first bad version is, then it would be easier to find when the problem started, and what commit caused it. Also, it is possible a bug might not affect everybody.

[Goodwin]

10 hours ago, roytam1 said:

Those builds are originally for my private use

 I appreciate your work, so no offense.

I downloaded your first version basilisk52-g4.1.win32-git-20180224-dc7ceccf8-xpmod it already has this defect.
And to check it is enough even just to throw mp4 file on browser tab and change playback speed in player.

While checking noticed that for example in basilisk52-g4.1.win32-git-20180224-dc7cececcf8 CPU load during normal playback is lower than for example basilisk52-g4.6.win32-git-20200725-4d76d4e-uxp-1e0bb1d35-xpmod. The difference is very small, 2-5%.

In general I realized that you do not want to fix or can not, too bad.

[Leokids123]

9 hours ago, Nicholas McAnespy said:

@Goodwin @roytam1 I'm not a professional, I just compile Mozilla based browsers for my personal use and hope for the best. For instance, I'm trying to compile Firefox 13+ with Windows 2000 compatibility. One thing that sometimes (but not always) causes runtime execution failure is clicking on tools -> options -> applications which can cause an error in MSVCR71.DLL. Also, after reverting the commit that broke Windows 2000 compatibility, I had a minor problem that is caused by opening a new tab, and the message displayed on the new tab page was relating to an invalid address. That annoyance was caused by the commit for Mozilla bug 728429, which mandated ASLR on Windows. In order to find that, I had to cherry-pick a range of commits between the one that broke Windows 2000 compatibility, and the one mandating ASLR, then compile the source code a few times to narrow down my search. The point is, if a problem does not exist in one of roytam1's browser builds, then exists on a later browser version, the right thing to do is find out what the last good version, and the first bad version is, then it would be easier to find when the problem started, and what commit caused it. Also, it is possible a bug might not affect everybody.

No offense but where's the Retrozilla 2.3 changes for Crescent-Vine,and also,where's the pull request you said you would merge?