The recent 0.5.4 Nu Client supports data feeds. But, when I try to enter a feed, it crashes once I click “OK” and it begins to fetch the JSON data. The feed data seems to be persisting because, once I open the wallet again, it crashes within 60 seconds when it tries to fetch the feeds in the background (I’m guessing.)
I’m using the OS X client and am currently running v10.7.5. Are any other users experiencing this?
This is the first report I’ve hard of this problem.
I had not tried the app on a machine running 10.7.x (it was built on a 10.8.5 machine) so there’s a possible chance that it is environment related rather than a problem with the client, but let’s see if we can isolate the problem.
First thing I’ll need is the URL for the feed you are trying to enter. If I can get it to work on my development and production machines without a problem, I’ll see if I can build a new VM with 10.7.5 on it and try to replicate.
If I can reproduce it, we can take a look at the debug.log file that is generated and see what’s going on behind the scenes that is causing the crash.
A fresh OSX 10.8.5 (no updates run) with Nu 0.5.4 is able to accept and track against data feeds without crashing. We’re digging in deeper on @CoinGame’s system to see if we can identify the culprit because it isn’t something that is readily apparent.
I understand that my setup is old as far as an OS is concerned. If that’s the reason things are breaking and it works without incident on decently new versions, I’d totally get it if you just said “upgrade please ”.
Are you able to run Nu 0.5.3-RC3 and use the data feeds without having the application crash? You can safely run it concurrent with the 0.5.4 versions on the network for a short time as long as you aren’t minting with it. CG is able to successfully add data feeds to that version of Nu without crashing on the same machine that he’s having issues with 0.5.4 on.
If this is the Apple-generated error log, there shouldn’t be anything in there that would be a problem. Rather than publishing it to the entirety of the Internet, however, if you’d like to send it to me directly, you can email it to ben at cryptoassure.com.
The memory issue is a new one, too, but it has me wondering if the two are related in any way. I’m going to tune down my VM’s memory settings and see how low I can get it before I generate the same message. From your system profile it looks like you have 4GB of RAM which should be more than enough, but I don’t know what else you had running at the same time that may have resulted in a low memory condition.
We’ll keep digging. Thank you for sending those files and reporting that second issue.
Nothing to report back yet, unfortunately. I’m still trying to replicate it under different conditions to try to isolate the problem. Originally I thought it may be related to the version of OpenSSL or Curl installed on the machine, but even when @CoinGame updated his VM’s versions of those two libraries to match what I used on the machine that compiled the Nu binary he was seeing the same problem.
I should have more time this week to dig in further. I’ll compile a new test release on a different OSX machine, too, so we can try to see if that makes any difference.