mockingbird Posted March 11, 2022 Posted March 11, 2022 20 hours ago, DanR20 said: That pref doesn't exist in my setup so it probably only shows if it's blacklisted?? For me it didn't make much difference changing those settings, the slowdown in performance wasn't affected. It might help others though. @DanR20 Thanks, actually it's "gfx.blacklist.layers.direct3d9" that needs to be reset to null... The problem is that it keeps setting itself again to "3" which blocklists it. In the failure log of about:support, I see this error: "CompositorD3D9::CreateRenderTargetFromSource: Failed to update texture Error code: 2289436780" I don't think that's too important, the compositor is probably still working fine even with this error, but is this what keeps triggering "gfx.blacklist.layers.direct3d9"? @grey_rat Thanks, I was unaware WebGL2 could be enabled as well under XP. "webgl.bypass-shader-validation" and "webgl.disable-angle" fixed this and it is now showing as enabled.
UCyborg Posted March 11, 2022 Posted March 11, 2022 I wouldn't classify the error as non important, correct operation would result in exactly zero errors, which is what you normally see anyway with good GPU and graphics driver. 1
grey_rat Posted March 11, 2022 Posted March 11, 2022 I had such an error, but I am applying a lot of changes in about:config it does not appear now Try to do this: gfx.direct2d.disabled - true gfx.work-around-driver-bugs - false gl.ignore-dx-interop2-blacklist - false layers.amd-switchable-gfx.enabled - false layers.child-process-shutdown - true if browser.tabs.remote.force-enable true layers.async-pan-zoom.enabled - switch false or true (if browser.tabs.remote.force-enable true) layers.deaa.enabled - false layers.gralloc.disable - true layers.prefer-d3d9 - true layers.shared-buffer-provider.enabled - true What of graphics card do you have? browser.tabs.remote.force-enable true? 1
mockingbird Posted March 11, 2022 Posted March 11, 2022 @UCyborg Thanks, noted. @grey_rat Thanks, much appreciated. I followed your settings and that seems to have removed the errors Yes, "browser.tabs.remote.force-enable" is "true" and it is showing as enabled: GPU Accelerated Windows 1/1 Direct3D 9 (OMTC) My GPU spec is as follows: Active Yes Description NVIDIA GeForce GTX 745 Vendor ID 0x10de Device ID 0x1382 Driver Version 10.18.13.5598 Driver Date 9-13-2015 Drivers nv4_disp Subsys ID 249a174b RAM Unknown Diag results: Diagnostics AzureCanvasAccelerated 0 AzureCanvasBackend cairo AzureContentBackend cairo AzureFallbackCanvasBackend skia Decision Log HW_COMPOSITING force_enabled by user: Force-enabled by prefs D3D11_COMPOSITING disabled by user: Disabled due to user preference for Direct3D 9 D3D9_COMPOSITING force_enabled by user: Hardware compositing is force-enabled DIRECT2D unavailable by default: Direct2D requires Direct3D 11 compositing D3D11_HW_ANGLE unavailable by default: D3D11 compositing is disabled disabled by env: D3D11 compositing is disabled Thanks to you all. Everything is running much better now... Google drive spreadsheets, PDF Viewer, loading pages, etc... 1
XPerceniol Posted March 11, 2022 Posted March 11, 2022 26 minutes ago, grey_rat said: I had such an error, but I am applying a lot of changes in about:config it does not appear now Try to do this: gfx.direct2d.disabled - true gfx.work-around-driver-bugs - false gl.ignore-dx-interop2-blacklist - false layers.amd-switchable-gfx.enabled - false layers.child-process-shutdown - true if browser.tabs.remote.force-enable true layers.async-pan-zoom.enabled - switch false or true (if browser.tabs.remote.force-enable true) layers.deaa.enabled - false layers.gralloc.disable - true layers.prefer-d3d9 - true layers.shared-buffer-provider.enabled - true What of graphics card do you have? browser.tabs.remote.force-enable true? Thank you ... I've used your suggestions and I've noticed improvement on my system and I'm dealing with a old low end graphics card and faulty memory and old drivers. For my old hardware, I've got it 'as good as its gonna get' and just making the most of it while it lasts. Take good care :)
XPerceniol Posted March 11, 2022 Posted March 11, 2022 (edited) layers.allow-d3d9-fallback;false (default is true) layers.prefer-d3d9;false (default) media.wmf.disable-d3d9-for-dlls;igdumd64.dll: 8.15.10.2189, 8.15.10.2119, 8.15.10.2104, 8.15.10.2102, 8.771.1.0; atiumd64.dll: 7.14.10.833, 7.14.10.867, 7.14.10.885, 7.14.10.903, 7.14.10.911, 8.14.10.768, 9.14.10.1001, 9.14.10.1017, 9.14.10.1080, 9.14.10.1128, 9.14.10.1162, 9.14.10.1171, 9.14.10.1183, 9.14.10.1197, 9.14.10.945, 9.14.10.972, 9.14.10.984, 9.14.10.996 (default) Do you think this looks right for Serpent 52 Build ID: 20220119024756? Edited March 11, 2022 by XPerceniol
grey_rat Posted March 11, 2022 Posted March 11, 2022 (edited) If the memory is more than 2Gb, you can increase the number of processes to 8. The browser will work faster dom.ipc.processCount XPerceniol, d3d10 or d3d11 does not work in windows XP. layers.prefer-d3d9 it is advisable to make an true. media.wmf does not work in windows XP (media.wmf.enabled - false). Edited March 11, 2022 by grey_rat 1
XPerceniol Posted March 11, 2022 Posted March 11, 2022 (edited) 8 hours ago, UCyborg said: I wouldn't classify the error as non important, correct operation would result in exactly zero errors, which is what you normally see anyway with good GPU and graphics driver. Yeah, I'm basically doing the opposite and relying on the software settings seeing as I have an awful graphics card and my computer is held together with duct tape and super glue Actually, I had to press f1 for help the other day, and ... I got a box warning that read: Quote "Dude, you are WAY beyond help - press F1 again and back away from the machine and somebody will be by to get you as you are not allowed to operate heavy machinery any longer." Edited March 11, 2022 by XPerceniol
XPerceniol Posted March 11, 2022 Posted March 11, 2022 (edited) 6 hours ago, XPerceniol said: layers.allow-d3d9-fallback;false layers.prefer-d3d9;false media.wmf.disable-d3d9-for-dlls;igdumd64.dll: 8.15.10.2189, 8.15.10.2119, 8.15.10.2104, 8.15.10.2102, 8.771.1.0; atiumd64.dll: 7.14.10.833, 7.14.10.867, 7.14.10.885, 7.14.10.903, 7.14.10.911, 8.14.10.768, 9.14.10.1001, 9.14.10.1017, 9.14.10.1080, 9.14.10.1128, 9.14.10.1162, 9.14.10.1171, 9.14.10.1183, 9.14.10.1197, 9.14.10.945, 9.14.10.972, 9.14.10.984, 9.14.10.996 Do you think this looks right for Serpent 52 Build ID: 20220119024756? K ... media.wmf.decoder.thread-count;-1 (Default) media.wmf.disable-d3d11-for-dlls;igd11dxva64.dll: 20.19.15.4463, 20.19.15.4454, 20.19.15.4444, 20.19.15.4416, 20.19.15.4404, 20.19.15.4390, 20.19.15.4380, 20.19.15.4377, 20.19.15.4364, 20.19.15.4360, 20.19.15.4352, 20.19.15.4331, 20.19.15.4326, 20.19.15.4300; igd10iumd32.dll: 20.19.15.4444, 20.19.15.4424, 20.19.15.4409, 20.19.15.4390, 20.19.15.4380, 20.19.15.4360, 10.18.10.4358, 20.19.15.4331, 20.19.15.4312, 20.19.15.4300, 10.18.15.4281, 10.18.15.4279, 10.18.10.4276, 10.18.15.4268, 10.18.15.4256, 10.18.10.4252, 10.18.15.4248, 10.18.14.4112, 10.18.10.3958, 10.18.10.3496, 10.18.10.3431, 10.18.10.3412, 10.18.10.3355, 9.18.10.3234, 9.18.10.3071, 9.18.10.3055, 9.18.10.3006; igd10umd32.dll: 9.17.10.4229, 9.17.10.3040, 9.17.10.2857, 8.15.10.2274, 8.15.10.2272, 8.15.10.2246, 8.15.10.1840, 8.15.10.1808; igd10umd64.dll: 9.17.10.4229, 9.17.10.2857, 10.18.10.3496; isonyvideoprocessor.dll: 4.1.2247.8090, 4.1.2153.6200; tosqep.dll: 1.2.15.526, 1.1.12.201, 1.0.11.318, 1.0.11.215, 1.0.10.1224; tosqep64.dll: 1.1.12.201, 1.0.11.215; nvwgf2um.dll: 22.21.13.8253, 22.21.13.8233, 22.21.13.8205, 22.21.13.8189, 22.21.13.8178, 22.21.13.8165, 21.21.13.7892, 21.21.13.7878, 21.21.13.7866, 21.21.13.7849, 21.21.13.7654, 21.21.13.7653, 21.21.13.7633, 21.21.13.7619, 21.21.13.7563, 21.21.13.7306, 21.21.13.7290, 21.21.13.7270, 21.21.13.7254, 21.21.13.6939, 21.21.13.6926, 21.21.13.6909, 21.21.13.4201, 21.21.13.4200, 10.18.13.6881, 10.18.13.6839, 10.18.13.6510, 10.18.13.6472, 10.18.13.6143, 10.18.13.5946, 10.18.13.5923, 10.18.13.5921, 10.18.13.5891, 10.18.13.5887, 10.18.13.5582, 10.18.13.5445, 10.18.13.5382, 10.18.13.5362, 9.18.13.4788, 9.18.13.4752, 9.18.13.4725, 9.18.13.4709, 9.18.13.4195, 9.18.13.4192, 9.18.13.4144, 9.18.13.4052, 9.18.13.3788, 9.18.13.3523, 9.18.13.3235, 9.18.13.3165, 9.18.13.2723, 9.18.13.2702, 9.18.13.1422, 9.18.13.1407, 9.18.13.1106, 9.18.13.546; atidxx32.dll: 21.19.151.3, 21.19.142.257, 21.19.137.514, 21.19.137.1, 21.19.134.1, 21.19.128.7, 21.19.128.4, 20.19.0.32837, 20.19.0.32832, 8.17.10.682, 8.17.10.671, 8.17.10.661, 8.17.10.648, 8.17.10.644, 8.17.10.625, 8.17.10.605, 8.17.10.581, 8.17.10.569, 8.17.10.560, 8.17.10.545, 8.17.10.539, 8.17.10.531, 8.17.10.525, 8.17.10.520, 8.17.10.519, 8.17.10.514, 8.17.10.511, 8.17.10.494, 8.17.10.489, 8.17.10.483, 8.17.10.453, 8.17.10.451, 8.17.10.441, 8.17.10.436, 8.17.10.432, 8.17.10.425, 8.17.10.418, 8.17.10.414, 8.17.10.401, 8.17.10.395, 8.17.10.385, 8.17.10.378, 8.17.10.362, 8.17.10.355, 8.17.10.342, 8.17.10.331, 8.17.10.318, 8.17.10.310, 8.17.10.286, 8.17.10.269, 8.17.10.261, 8.17.10.247, 8.17.10.240, 8.15.10.212; atidxx64.dll: 21.19.151.3, 21.19.142.257, 21.19.137.514, 21.19.137.1, 21.19.134.1, 21.19.128.7, 21.19.128.4, 20.19.0.32832, 8.17.10.682, 8.17.10.661, 8.17.10.644, 8.17.10.625; nvumdshim.dll: 10.18.13.6822 media.wmf.enabled;true media.wmf.low-latency.enabled;false EDIT: media.wmf.skip-blacklist;falsemedia.wmf.vp9.enabled;false These are all at their defaults and thank you in advance for any help. Answered - Thank you @grey_rat I will leave d3d9 prefs at false as well as d3d11 prefs and media.wmf prefs on my XP system. Edited March 11, 2022 by XPerceniol
mockingbird Posted March 11, 2022 Posted March 11, 2022 (edited) @grey_rat I spoke to soon about the errors in the log not being there. Sure enough this shows up again: "CompositorD3D9::CreateRenderTargetFromSource: Failed to update texture Error code: 2289436780" ...and it's still flagging "Blocklisted; failure code BLOCKLIST_FEATURE_FAILURE_DL_BLACKLIST_g37" when that happens... Is there a way to tell Serpent to ignore the error? The problem is that every time that happens it also sets "gfx.blacklist.layers.direct3d9" to "3", when it should be null. Thanks for the process count tip. Indeed this XP machines has 4GB (modded XP)... We'll see if upping that to 8 helped as well. Edited March 11, 2022 by mockingbird
TrevMUN Posted March 11, 2022 Posted March 11, 2022 On 3/4/2022 at 3:51 AM, Reino said: I believe StackOverflow.com has updated their javascript code. I'm using the latest NM28 ('palemoon-28.10.4a1.win32-git-20220226-ba47fad4d-uxp-c403014cb-xpmod-sse.7z') and I can't post answers or add comments anymore. Has anyone else experienced this? On 3/4/2022 at 3:59 AM, InterLinked said: Yup, it was working for me in Chromium 70 with the latest Chromefill (https://github.com/InterLinked1/chromefill) until about 2 days ago. Looks like one of those "Unexpected syntax ." errors in both Chromium 70 and New Moon. Unfortunately, this will be difficult to polyfill. Probably not even anyone at SO responsible directly, but one of the stupid libraries used somewhere on the site, so they don't even know it's happening. I'd think posting answers would work since JS isn't required, but yeah, comments, voting, etc. definitely is broken now. I've been having the same problems on Coinbase, BlockFi, and LinkedIn. Coinbase and BlockFi stopped working on New Moon 28 a few months ago. A few days ago LinkedIn stopped working as well. I had ONE tab that was still open which allowed me to still receive and send messages, but this morning Kaiser Permanente's website caused New Moon to lock up and I had to kill the process, which of course meant when I relaunched New Moon that my last remaining LinkedIn tab no longer works. This sucks.
TrevMUN Posted March 11, 2022 Posted March 11, 2022 On 3/4/2022 at 3:51 AM, Reino said: I believe StackOverflow.com has updated their javascript code. I'm using the latest NM28 ('palemoon-28.10.4a1.win32-git-20220226-ba47fad4d-uxp-c403014cb-xpmod-sse.7z') and I can't post answers or add comments anymore. Has anyone else experienced this? On 3/4/2022 at 3:59 AM, InterLinked said: Yup, it was working for me in Chromium 70 with the latest Chromefill (https://github.com/InterLinked1/chromefill) until about 2 days ago. Looks like one of those "Unexpected syntax ." errors in both Chromium 70 and New Moon. Unfortunately, this will be difficult to polyfill. Probably not even anyone at SO responsible directly, but one of the stupid libraries used somewhere on the site, so they don't even know it's happening. I'd think posting answers would work since JS isn't required, but yeah, comments, voting, etc. definitely is broken now. I've been having the same problems on Coinbase, BlockFi, and LinkedIn. Coinbase and BlockFi stopped working on New Moon 28 a few months ago. A few days ago LinkedIn stopped working as well. I had ONE tab that was still open which allowed me to still receive and send messages, but this morning Kaiser Permanente's website caused New Moon to lock up and I had to kill the process, which of course meant when I relaunched New Moon that my last remaining LinkedIn tab no longer works. This sucks. New Moon 28 is the browser I turn to when sites stop working on my other browsers.
TrevMUN Posted March 11, 2022 Posted March 11, 2022 (edited) Accidental double post. Edited March 11, 2022 by TrevMUN
XPerceniol Posted March 11, 2022 Posted March 11, 2022 (edited) 5 hours ago, XPerceniol said: .... Shucks, I accidentally posted when I meant to correct my posting. Sorry. Edited March 11, 2022 by XPerceniol
Recommended Posts