when I try $chromedriver on my installation of OS X Lion I get this error message:
Starting ChromeDriver (v2.2) on port 9515
objc[5006]: Object 0x1215940 of class NSThread autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
Bus error: 10
What can I do to fix this?
I used an earlier version of Chromedriver (v2.1) and it worked.
Related
I'm running PyDev 6.4.1.2 on Eclipse EE Neon (4.6.3) on OS X 10.11.6 (El Capitan)
Whenever I update the PYTHONPATH and syncing is attempted, I get 3 warnings that Python has crashed. The updated PYTHONPATH still works, but I was wondering what the possible cause of this could be.
Thank you.
The reason it crashes is because when doing some_module = __import__("some.module"), dir(some_module), that module is crashing and usually means an error in compilation of such module or some wrong environment variable (so, the module is not being properly initialized).
I'm not sure PyDev prints which module was the culprit... do you have some error in your error log after the crash happens?
http://www.pydev.org/faq.html#HowdoIReportaBUG has instructions on finding the error log.
I am puzzled: when I am running EPIC Perl debugging tool it produces "Timed out while waiting for Perl debugger connection" error along with "Unable to connect to remote host: 192.168.1.37:5000
Compilation failed in require...." on the console.
I am on OS X 10.11.1 (El Capitan, darwin 15.0), using Eclipse Kepler 4.3.2, EPIC 0.7.0 (same thing happens with 6.5.6), and Perl 5.18 (prebuilt for darwin) or ActiveState Perl 5.20
Do you have any suggestions?
Thanks in advance.
It looks like I found the answer. The IP address mentioned in the error message is the one that I had statically added in the hosts file. For some reasons EPIC searches this address for debugger connection skipping dynamic addressing assigned by DHCP.
I have installed the latest version of ADT (Android Developer Tools Build: v21.1.0-569685) and eclipse 3.8. I followed the instructions (http://developer.android.com/training/basics/firstapp/running-app.html#Emulator) to start the Hello World example but the AVD crashes on start, with no error messages in the console.
I tried that and even lower RAM to 40M but still no luck. I tried all kinds of combinations of RAM and resolution (lowered resolution to 480 x 800 hdpi), camera settings, enabling "Run as Admin". It just crashes w/ a message "emulator-arm.exe has stopped working". The console doesn't show any error message.
I have tried many solutions that came up on Google but no dice; plus a lot of them are very old posts. Please help!
Please see screen shot of my configurations and crash message here:
http://imgur.com/a/mvogh
My machine:
Win 7 64
RAM: 8GB
Processor: AMD Phenom(tm) II X6
Graphics card: ATI Radeon HD 5450
This is what I see when it crashes:
emulator-arm.exe has stopped working
problem details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: emulator-arm.exe
Application Version: 0.0.0.0
Application Timestamp: 5111a505
Fault Module Name: atioglxx.dll
Fault Module Version: 6.14.10.9232
Fault Module Timestamp: 4b208022
Exception Code: c0000005
Exception Offset: 0000b212
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I tried running "adb logcat" and screen said "waiting for device". I started Eclipse and started AVD from AVD manager. It crashed again but "adb logcat" still said waiting for device.
Is it possibly a hardware issue?
Thanks.
I installed latest driver/software from ATI and everything worked. Thanks.
If you need to debug any given Android instance, from both real devices or from the AVDs, use adb logcat, other than that, your question it's really without any specific detail that can help with this.
I have a weird problem since a few days. After exporting a project for android once it works fine the 2nd export I do eclipse crashes with this error:
Identifier: org.eclipse.eclipse
Version: 3.8 (3.8)
Code Type: X86-64 (Native)
Parent Process: launchd [269]
Date/Time: 2013-03-12 21:36:13.365 +0100
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 321292 sec
Crashes Since Last Report: 3
Per-App Interval Since Last Report: 44806 sec
Per-App Crashes Since Last Report: 2
Anonymous UUID: 52A136CA-CDAE-4661-B166-51B04A18C21C
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x000000011f1c965f
Crashed Thread: 46 Java: ModalContext
Any clues. Running: adt-bundle-mac-x86_64-20130219
SIGBUS looks like bad RAM but then other things would act up aswell?
B
I guess that's random. As mentioned in this thread it looks like it can happen if eclipse is building your project at the same time as you're exporting it. You could try to disable the "build automatically" option in eclipse while you're exporting it.
I have an old Rails 2.3.2 application that I just ported to my new Mac running OS X Lion.
When I launch the server (script/server) it prints out the following two lines
[2012-01-05 18:19:26] INFO WEBrick 1.3.1
[2012-01-05 18:19:26] INFO ruby 1.8.7 (2011-02-18) [i686-darwin9.8.0]
but then there is a very long delay before it prints out:
[2012-01-05 18:20:26] INFO WEBrick::HTTPServer#start: pid=5792 port=3000
There must be something wrong.
How can I fix this problem?
It turns out that the compiler for Lion for Ruby has changed and Developer Tools 4.2 does not include it so I had to download the fix.
From here:
If you're running a fresh copy of Lion & Xcode 4.2, you're going to need to install the GCC 4.2 dev libraries first - they aren't included in a fresh Xcode 4.2 install.
Once I recompiled my Ruby then everything worked properly.