tag:support.primatelabs.com,2011-01-31:/discussions/geekbench/24294-geekbech-42-crash-on-launch-macbook-pro-mid-2014Primate Labs: Discussion 2018-02-05T17:42:31Ztag:support.primatelabs.com,2011-01-31:Comment/446590932018-02-04T02:32:07Z2018-02-04T02:32:09ZGeekbech 4.2 crash on launch MacBook Pro Mid 2014<div><p>According to Google this is just a straight up example of bad coding:</p>
<p>"The error message indicates a pointer to a block of freed memory doesn't actually point to free memory. (Either the pointer itself has been changed in some way, or the memory it points to has been overwritten in a way that clobbers a consistency check.)</p>
<p>The most likely cause is that the memory is a freed object instance, but your code as an unretained reference to it and has tried to use it like a "live" instance. Or it may just be a block of non-object memory that has been modified after being freed.</p>
<p>That is to say, this is likely a memory management bug in your code."</p></div>BHtag:support.primatelabs.com,2011-01-31:Comment/446590932018-02-04T02:36:55Z2018-02-04T02:36:57ZGeekbech 4.2 crash on launch MacBook Pro Mid 2014<div><p>Found a copy of 4.1.3 .... It also crashes. Going to ask for my money back right about NOW!!!!</p></div>BHtag:support.primatelabs.com,2011-01-31:Comment/446590932018-02-04T04:42:23Z2018-02-04T04:42:24ZGeekbech 4.2 crash on launch MacBook Pro Mid 2014<div><p>OK ... solved. CUDA driver has to be latest version ...</p>
<p>It would be better if GeekBench didn't do a hard crash, and just told the user to update the CUDA drivers ...</p></div>BHtag:support.primatelabs.com,2011-01-31:Comment/446590932018-02-05T17:42:30Z2018-02-05T17:42:30ZGeekbech 4.2 crash on launch MacBook Pro Mid 2014<div><p>Hi,</p>
<p>Thanks for letting us know about this, and I'm sorry for any trouble this may have caused. I believe that we also spoke via email about this issue and about your refund request, but I'd like to follow up here as well. Could you let me know which of the following CPUs your MacBook Pro Mid 2014 has so that we can identify the device more specifically and investigate this problem?</p>
<p>1) Intel Core i7-4980HQ<br>
2) Intel Core i7-4870HQ<br>
3) Intel Core i7-4578U<br>
4) Intel Core i7-4770HQ<br>
5) Intel Core i5-4308U<br>
6) Intel Core i5-4278U</p>
<p>Would you also be able to let me know what your CUDA driver version is now, and (if you are able to determine this) what it was before updating?</p>
<p>All the best,<br>
Colin<br>
Primate Labs Inc.</p></div>Colin