Flavours is not compatible with iDefrag (and probably iPartition)

Coriolis Systems

• May 26, 2014 09:59

For the second time in recent memory, we’re getting (lots) of bug reports from our users that are being caused by Flavours.

Please can you fix this as a matter of urgency? End users quite reasonably assume that crashes in a given piece of software are caused by a bug in that piece of software, but by injecting your code into our application and causing a crash, the reports are going to the wrong place.

CrashLog-lku73J.log
CrashLog-oVbchL.log
CrashLog-wnzGOH.log
CrashLog-xwsoNk.log
CrashLog-bXgkqy.log
CrashLog-dYhtaf.log
CrashLog-dYUqKZ.log
CrashLog-FdEUaS.log

0

• 

  Pedro Grilo

  • May 26, 2014 11:19

  Thank you for letting us know of this issue and sorry the trouble.

  We will provide a fix on the next update! 

  In the meanwhile the issue can be avoided by excluding iDefrag from Flavours:

  Go to menu Flavours > Troubleshooting... > Exclude applications... and select iDefrag.

  We apologize for the inconvenient.

   

   

  0

Please sign in to leave a comment.