-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incorrect checksum for freed object #78
Comments
It looks like a problem with Ruby. What version are you running and is it one that came with OS X or one you installed separately? |
I appreciate your quick reply, Alex! |
actually I ended up getting the latest tuneup js by clone from git hub directly but not through cocoapods |
I believe this is not the new tuneup script issue, the same error happens if I switch back to old tuneup script, interesting thing is, if I keep trying RunTestCase.sh, it will pass the error after a few try, but eventually it will fail at later steps (I think it's Instruments path) |
even I run >ruby -v |
Are you running the stock Ruby, or one you installed yourself? |
i am not sure, i didn't do any configuration, should I use which one? and how can I specify? |
I fixed the ruby issue by installing Ruby 2.1.4, new issues shows up: Launching instruments. Will retry 0 more times if it doesn't initialize2014-10-29 15:32:14.736 instruments[63836:226173] WebKit Threading Violation - initial use of WebKit from a secondary thread. |
I updated to iOS 8 SDK, and also updated tuneup js, but I got following error when I try to run automation:
ruby(22747,0x7fff76253300) malloc: *** error for object 0x100801a08: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
./runTestCase.sh: line 119: 22747 Abort trap: 6 $BASEDIR/automation/tests/tuneup/test_runner/run $PROJECT $BASEDIR/automation/tests/$PROJECT/$TESTCASE.js $BASEDIR/automation/results/ $TEMPLATE_OPTION $PLATFORM_OPTION -c -v
any idea? Thanks/
The text was updated successfully, but these errors were encountered: