![]() ![]() Use it: env DYLD_INSERT_LIBRARIES=/path/to/patch.dylib "/path/to/Google Chrome.I have tried this on 3 USB drives. Return [self _initWithPreviousTouch:touch newPhase:phase position:position isResting:isResting it: clang -dynamiclib -framework AppKit patch.m -o patch.dylib ![]() (id)_initWithPreviousTouch:(NSTouch *)touch newPhase:(NSTouchPhase)phase position:(CGPoint)position isResting:(BOOL)isResting (id)_initWithPreviousTouch:(NSTouch *)touch newPhase:(NSTouchPhase)phase position:(CGPoint)position isResting:(BOOL)isResting NSTouch (Patch_10_10_2) _attribute((constructor)) void patch NSTouch () Put the following in a file "patch.m": #import Option 2 of Pippyn's answer works so giving the full temporary fix (I can't just upvote the answer): I imagine a patch will be pushed out to canary builds over the next couple of days or Apple will send out a new driver update (but probably not since they were working to remove isResting). Not sure if this would work, but it might be a good try. You could try downgrading Chrome if the former option sounds like a hassle. If this sounds like a good solution, make sure you also enable “Ignore trackpad when mouse.” in Accessibility settings. It looks like some people are simply plugging in external mice and if they don't touch the trackpad, it's fine. But according to this, the problem stems from Apple depreciating the isResting selector and then completely removing it in the most recent update.Īgain, the error people are reporting looks like this: : unrecognized selector sent to instance Judging by the amount of attention chromium issues has gotten over the past few days, it looks like the problem you are describing is caused by an issue with the Mac touch pad driver.īut this is a weird bug because it's clearly not affecting everyone, even people with the most updated version of Mac OS X (10.10.2). ![]() I suppose that if the fix works, you could 'cherry pick' files and folders from the backup directory until it starts having the problem again to narrow down the file that might be the root cause of the crashing. Turn on Chrome sync before you start this process if you are worried about losing anything. It should generate a new default profile and hopefully your problem will be fixed.ĭoing this, however, will cause you to lose your data. Rename the folder Default to something like Default-Backup and relaunch Chrome. Navigate to: ~/Library/Application Support/Google/Chrome/ It's possible they might have been corrupted or damaged. This would make sense since uninstalling and reinstalling the application in Mac would not remove these user files. I know I've had this problem before on a Windows PC. This could be an issue with your user profile in Chrome. I've also tried to delete Chrome from the Apps folder and install it again, but no success either. Someone is trying to raise an exception! NSInvalidArgumentException reason -: unrecognized selector sent to instance 0x7fb71afabcc0 18:02:09.266 Google Chrome -: unrecognized selector sent to instance 0x7fb71afabcc0 I've tried to launch a safe session of Chrome with the "-safe-plugins" options without success, here is what happens when I do this from the terminal: Mac-705681ad12c1-2:MacOS javipas$. Everytime I try to launch it quits with the message "Google Chrome has quit unexpectedly", giving me the option to send a report to Apple, Ignore, or restart Chrome. A few hours ago Chrome closed on my MacBook Air with OS X Yosemite 10.10.2 and there's no way to recover it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |