background

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Buy bitcoins anywhere in the world at localbitcoins.com

Buy Monero at local Monero

Trade BTC for Monero at AgoraDesk

Use Anonymous Ads
Use Anonymous Ads

MacMiner 1.5.14 released - lots of change!

edited February 2014 in General
Quite a nice release for you today! MacMiner 1.5.14:

• Adds CPU miner support for VertCoin VTC and QuarkCoin QRK! 

• New Pool settings panel in Preferences - for the moment in conjunction with legacy pool settings window 

• Improves update notifications to support 10.6 and links them to the 'Check for updates' menu item 

• Bug fixes and improvements

Please let me know how you get on with the changes!

Comments

  • Just downloaded this version on my MacPro4,1 running Mac OS X 10.9.1 (13B42). It consistently crashes at startup.
  • Ack, can you post the error here when it asks you whether you want to report the crash please?

    Better luck with an earlier version?
  • I posted a b version of 1.5.14 which fixed this issue on a VM I managed to replicate it on, please let me know how you get on!
  • edited February 2014
    The previous version 1.5.13 is working fine. Here is the crash report for the 1.5.14. I am only posting the top part of the report as it is too long to be posted here. If you need the whole thing, I can send it by email.

    Process:         MacMiner [449]
    Path:            /Applications/BitCoins/MacMiner.app/Contents/MacOS/MacMiner
    Identifier:      com.fabulouspanda.macminer
    Version:         1.5.14 (1514)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [192]
    Responsible:     MacMiner [449]
    User ID:         501

    Date/Time:       2014-02-13 10:02:42.074 +0700
    OS Version:      Mac OS X 10.9.1 (13B42)
    Report Version:  11
    Anonymous UUID:  0FE4E625-36A1-BF70-7CB6-4A42140788BF


    Crashed Thread:  0  Dispatch queue: com.apple.main-thread

    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000

    Application Specific Information:
    *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: aString != nil'
    terminating with uncaught exception of type NSException
    abort() called
  • That's the bug I saw - 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: aString != nil' is the important part

    it should be fixed in b
    Unfortunately I didn't change the build number so I'm not sure whether you got that :S
  • edited February 2014
    I haven't tried the latest version 1.5.14b. I will try both 1.5.14 and 1.5.14b on my laptop (MacBookPro) as I left home and have no longer access to my MacPro, until tonight. Will let you know how it goes.

    FYI, I did notice something peculiar. When you asked me to send you the crash report, I had already downgraded to 1.5.13. I therefore installed 1.5.14 back again in order to send you the report. This time however it didn't crash. I assumed that perhaps it had to do with some config files that were left behind by 1.5.13. So I decided to use AppZapper to completely get rid of any pref. files left by MacMiner. I then rebooted and installed 1.5.14 again. At this point the app started crashing again and this is how I could send you the report.
  • My theory is that I knocked an 'if' out somewhere as there were extensive changes in 1.5.14 and it was trying to set a nil string from the non existent pref for log length, which is what fixed it for me in my test environment with 1.5.14b

    thanks for the updates, and the detailed testing!
  • I should add that curiously, deleting the prefs didn't cause the crash for me on any of my real machines, only on a VM, for some reason…
  • edited February 2014
    No pbs at all.

    I did try 1.5.14 on my MacBookPro (MacBookPro8,2) this time. I had 1.5.13 installed previously so 1.5.14 did not crash. Once I completely deleted 1.5.13 and all associated files, then 1.5.14 would start crashing. Below the crash report on my MacBookPro for reference (same crash error as on the MacPro):

    Process:         MacMiner [303]
    Path:            /Applications/Coins/*/MacMiner1.5.14.app/Contents/MacOS/MacMiner
    Identifier:      com.fabulouspanda.macminer
    Version:         1.5.14 (1514)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [169]
    Responsible:     MacMiner [303]
    User ID:         501

    Date/Time:       2014-02-13 11:27:33.783 +0700
    OS Version:      Mac OS X 10.9.1 (13B42)
    Report Version:  11
    Anonymous UUID:  61D3919C-631E-7A61-DC84-EEBB80CE90F9


    Crashed Thread:  0  Dispatch queue: com.apple.main-thread

    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000

    Application Specific Information:
    *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: aString != nil'
    terminating with uncaught exception of type NSException
    abort() called
  • edited February 2014
    I have been testing 1.5.14b and it seem to be working fine. However, I noticed something strange. in the 'Pool Setup Window' the LTC address has beed replaced with my LTC worker username. This also happened on 1.5.13 but I haven't been able to reproduce this consistently. It is actually the second time I see this.
  • edited February 2014
    Glad to hear that fixed it, thanks for confirming it! The pool setup window is deprecated and kept as a legacy method, but the Pool settings panel of the Preferences window which is new in 1.5.14 is recommended from here on, unless you specifically want to set up the backup pools
  • No worries. That window should perhaps be dropped then as it is confusing, and as yourself said, deprecated.
  • edited February 2014
    Hi again. More comments.

    I have been testing the app. I have another comment regarding the Pool Settings Panel of the Preferences. There seems to be a bug regarding Scrypt coins set up. I am trying to setup a Scrypt account. After I fill the pool address, my username and password and click save, it seem the app is actually not saving the information properly. How I know? Well, If I select another type of cryptocurrency, lets say SHA-256, and then come back to Scrypt, the username and password are gone and the pool address is back to the default (pool.fabulouspanda.co.uk:9327). If I try to run the CPUminer it will actually tell me that the cpu has started and that the primary pool is set to the actual pool and username I provided in the pool settings panel of the Preferences but when I click "Indeed" I receive the following error:

    [2014-02-13 13:33:36] HTTP request failed: Empty reply from server

    [2014-02-13 13:33:36] json_rpc_call failed, retry after 30 seconds


    The only way I have managed to successfully setup a Scrypt pool account is by doing it through the deprecated Pool Setup window and making sure I also fill in the LTC address if not it will by default use pool.fabulouspanda.co.uk:9327.  
  • Arg, you're right, it's bugged out! The other coins set up fine in the prefs but I need to release a quick fix for that - luckily it's something stupid so It'll be fixed very soon, thanks for the report!
  • That bug wouldn't have affected set up by the way, just restoring saved pool for scrypt in prefs. It's fixed now in 1.5.14c, thanks for the bug report!
  • No worries, my pleasure. Will try out 1.5.14c.
  • Thanks for s great program!!!

    How do I download the beta releases?

    Ken
  • Hey Ken, no problem :) 

    All the versions (except lots of earlier minor releases) are up at 

    I actually stopped separating beta and stable versions after all the new ASIC miners being released in quick succession would have prevented people using the older, 'stable' version from mining with newer devices.

    There are occasions however when the Github project has a few code changes beyond the released versions, but it doesn't happen very often:
  • I see that 2 new versions have been released. That was fast! Loosing track :D

    Will have a look at those.
  • Hello everyone,

    Im running OS X 10.9.1 on a MacBook Air and have downloaded the most recent two versions of MacMiner to try the Maxcoin option. The latest version sparked up once, and now will no longer open, with a crash report very similar to the one described above. 

    Application Specific Information:
    *** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSConcreteScanner setScanLocation:]: Index 8 out of bounds; string length 0'
    terminating with uncaught exception of type NSException
    abort() called

    I honestly have no idea what that means, and it did fire up once...so Im mystified. Thought it might be useful for you to know.

    Cheers.
  • Oh no! Please try deleting

    /Users/you/Library/Preferences/com.fabulouspanda.macminer

    and try opening again, let me know whether that helps? The updates were quite big so I may well have overlooked something, I'll get code scanning!
  • Any info on what settings you set might help too!

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file