I have just installed the Selenium Remote Driver on my Mac OS X 10.8.5 machine, and using Firefox 43.0.4 (the latest stable to date) when running this code:
#!/usr/bin/perl
use strict;
use warnings;
use Selenium::Remote::Driver;
use Selenium::Firefox;
my $firefox = Selenium::Firefox->new;
$firefox->get('http://www.google.com');
causes the browser to open, and then crash, outputting the following error to console:
kernel[0]: firefox-bin (map: ...) triggered DYLD shared region unnest for map: ..., region ...->.... While not abnormal for debuggers, this increases system memory footprint until the target exits.
Any clue as to what might be causing this?
Is it a programming error on my part?
Should I be using some specific flag to prevent this?
Or is this something I should report as a bug?
Any help is much appreciated. You will have noticed this is my first post to the site. I hope it is not out of order in any way, please excuse me if it is.
Thank you in advance.
Best regards,
Mark.
This is probably related to an issue with Selenium and FX 43 64bit. As of now there is no fix, only workarounds. These include:
Updating to newest Selenium version which makes FX not check addon signatures.
Using 32 bit version of Firefox
Using an older version of Firefox, e.g. 42
See https://github.com/SeleniumHQ/selenium/issues/1431 for more details.
Related
I am working on a IddCx indirect Display Driver. I have run into a bug that I cant find any reason to blame my own code on. Every two seconds or so IddCxSwapChainReleaseAndAcquireBuffer takes over 100ms, up to 8000ms to complete. It normally takes below 16ms to complete (depends on your frame rate).
I even added timestamps to the IddCx Sample code from Microsoft. It still has this issue, so it cant be a fault with my own code. I have exhausted most of my debugging options.
Changing IddCx versions I am compiling with (1.4 to 1.8) by targeting the libs, the headers, and defining the macros (IDDCX_VERSION_MAJOR, IDDCX_VERSION_MINOR, IDDCX_MINIMUM_VERSION_REQUIRED). 1.9 btw doesnt seem to run well, IddCxDeviceInitConfig() fails with Invalid Parameter if I choose version 1.9.
Changing which UMDF version I am compiling with (2.25 to 2.33).
Changing the Windows SDK version I am using (10.0.19041.0, 10.0.20348.0, 10.0.22000.0, 10.0.22572.0).
Swapping my OS to the Insider Program preview version of win11 (currently 22000.588 co_release).
Things I think may be solutions that I need help on.
When I am running the Driver, within dxdiag, the display says its using WDDM version 1.3, while my other displays use WDDM version 3.0. WDDM 1.3 is old, so maybe this could be causing issues? How do I tell visual studio to compile my driver to compile with WDDM version 3.0? Does my driver need to WHQL Logo'd first?
IddCxGetVersion() returns with version 1801 or 1803 no matter what I change (SDK, IDDCx version, etc), which is from 2018! So what am I doing wrong here to get the OS to choose to use a newer version of IddCx? This may be related to the WDDM version being 1.3 instead of 3.0.
Swapping back to Windows 10. I originally swapped to Windows 11 because the WDK dev environment is completely unstable, with the samples sometimes not creating functional drivers, that fail to call into 'EVT_IDD_CX_ADAPTER_INIT_FINISHED', I have confirmed its being compiled incorrectly (sometimes) on windows 10, and the old dlls from earlier that day will still work, but the new dlls will not. So thats why I am staying with Windows 11, I also need to swap to Windows 11 anyways since we should be moving forwards, not backwards.
forgot to close this.
Realized the issue was that the monitor desktop simply wasnt updating. So the OS was just rendering the desktop less often, resulting in less frames being pushed to the swapchain for me to grab
This may already have a question somewhere, but I am at a loss as to how to debug IE11 on my Mac.
I currently run a full Win10 instance in a Virtual Box, but it is so bloated that it is nearly impossible to move nimbly between coding and debugging. IE dev-tools are also inaccessible using this method because it just cripples the VM, so I am flying blind with coding.
I have looked up tutorials as to how to run IE on a Mac direct using Wine/Remote Desktop, but these instructions are out of date or the supporting software does not work as intended. Also, Microsoft (being the evil empire that they are) discontinued support for debugging with Azure so that is another option off the table.
If there is anything that actually works without having to shell out $$$ please let me know as it is so painful currently to debug the worst browser that will never die.
From your description, I can see that you had already try to use the Windows 10 VM but it get hangs.
You can try to go to Windows Features on or off inside Control Panel-> Programs-> Programs and Features and try to turn off the features that you are not using may help to reduce the load.
It is possible that you are running your VM in a very less memory that downs the performance of the OS.
If possible for you than try to install a VM with some more memory.
Otherwise you can try to install Windows 7 in your VM and upgrade to IE 11 in that.
It can help you to solve your issue with the OS and you can debug the code on IE 11.
Below are some helpful references that may give you some additional information.
How to test your website with Internet Explorer on a Mac
How to Debug in IE on a Mac
I am using Windows 10 (insider build) and Firefox 58.0.2. But all the browser detection sites like www.whatismybrowser.com and similar says that I am using Firefox 52 on Windows 7. Detection scripts also return wrong screen resolution.
Can anyone say why is that? Maybe some firefox plugin - but I am not using any that would do that, that I know of. Maybe uBlock Origin?
If you have the setting privacy.resistFingerprinting turned on in about:config, Firefox will pretend to be the most recent ESR version (in this case 52) on the most common OS (Windows 7).
This is to make your browser's user agent string the same as a lot of other people's, so it's harder for sites to use it to identify you.
https://bugzilla.mozilla.org/show_bug.cgi?id=1418672
I'm trying to use direct commands to gdb through xcode's console window when the program is paused. But the (gdb) prompt just accepts the carriage returns, and does nothing. Has anyone encountered this? I'm on the latest version of Mac OS X (10.6.2) with the XCode 3.2 beta.
If using a beta best to contact the beta mailing lists as this is the sort of issue the developers want to know.
If using a beta the first thing I would check is does this work using the previous production version
Also note that you might be under a NDA and so can only discuss with the developers.
This is a bug in the software, or an incompatibility with some setting in my system. Formatting my laptop and reinstalling the software fixed the problem.
I'm just starting out with GWT but I can't even run the getting started example without getting the following error:
Invalid memory access of location 0x10 eip=0x93624148
I am aware of the "java hosted mode 32 bit" stuff, anyway I tried every combination I could think of and still could not get away with that error.
I tried:
Using the eclipse plugin
Setting all possible jvm switches in eclipse to 1.5
Use the command line tool
Set the java environment to java 5 32 bit in the preference pane, and do all of the previous options again, without success (I checked that effectively "java -version" gives me the right 32 bit jvm)
Any suggestion? I can't believe that something which should be apparently immediate is so difficult ...
Thanks for your help
Best regards
Nicola Montecchio
Seems to be fixed in GWT 2.0.
Alternatively, try using the WebKit Nightly.
Steps here:
http://grack.com/blog/2009/11/16/fix-for-gwt-hosted-mode-crash-with-safari-4-0-4/
See release notes for latest SDK 1.7.1.
You might need to switch to Snow Leopard to get it working.
Update: GWT 2.0 is just out today. Give it a go, even thought I've not seen anything related to Leopard in the change list.
I used gwt a lot on my mac with OS X 10.5 on. It actually worked fine. Have you also set the java class version in the projects facets menu in the project preferences to java 5?
You can also provide which java to use in the launch configuration, you don't need to modify in the Mac OSX preference pane.
I actually upgraded to 10.6 when it came out, and it made life with GW easier.
Hope it helped, if you have any more questions let me know.
Best - István