GPUMAX | The Bitcoin Mining Marketplace

[rjk]

BTW, there is a major fail in one of the javascipt objects that is screwing my browser over. The page suddenly froze the entire browser, so I went to look at the memory usage and it was at --4GB-- yes 4 gigabytes. I was able to kill the offending script after waiting a bit and letting it time out, and the memory usage immediately dropped to 550MB.

[nave]

BTW, there is a major fail in one of the javascipt objects that is screwing my browser over. The page suddenly froze the entire browser, so I went to look at the memory usage and it was at --4GB-- yes 4 gigabytes. I was able to kill the offending script after waiting a bit and letting it time out, and the memory usage immediately dropped to 550MB.

The same thing has been happening to me. I'm pretty sure it has to do with the speed box on the worker page. If it's set to live the memory jumps up quick until the browser crashes, but if I switch it to 24H then everything works fine.

[rjk]

BTW, there is a major fail in one of the javascipt objects that is screwing my browser over. The page suddenly froze the entire browser, so I went to look at the memory usage and it was at --4GB-- yes 4 gigabytes. I was able to kill the offending script after waiting a bit and letting it time out, and the memory usage immediately dropped to 550MB.

The same thing has been happening to me. I'm pretty sure it has to do with the speed box on the worker page. If it's set to live the memory jumps up quick until the browser crashes, but if I switch it to 24H then everything works fine.

Well for me, once I killed the script and then refreshed the page, it started working again fine. However, when it froze up, I was on the edit page looking at the worker PPS rate, not the stats page with the speed.

One thing I noticed was that when I tried to change the PPS rate, it kept reverting back live, as if there was a socket.io connection pulling in the current price. But that didn't work as expected, because all it did was revert back to what I had set, instead of reverting to a given price. I assume that the same bit of javascript is used on both pages for socket connections, and that may be why the random memory leaks are happening on both pages.

[trouserless]

Anyone else just getting tons of Comm failures? 

yes


[2012-06-15 15:03:26] Pool 0 slow/down or URL or credentials invalid
[2012-06-15 15:03:26] Unable to get work from pool 0 http://gpumax.com:8332

double checked credentials - still no love

[yochdog]

Anyone else just getting tons of Comm failures? 

yes


[2012-06-15 15:03:26] Pool 0 slow/down or URL or credentials invalid
[2012-06-15 15:03:26] Unable to get work from pool 0 http://gpumax.com:8332

double checked credentials - still no love

I checked my back-up pool, and it works flawlessly.  Definitly GPUmax specific. 

[Math Man]

Anyone else just getting tons of Comm failures? 

yes


[2012-06-15 15:03:26] Pool 0 slow/down or URL or credentials invalid
[2012-06-15 15:03:26] Unable to get work from pool 0 http://gpumax.com:8332

double checked credentials - still no love

I checked my back-up pool, and it works flawlessly.  Definitly GPUmax specific. 

I've been getting 7-10% rejects when connected to my private pool through GPUMAX since the updates.

[yochdog]

Anyone else just getting tons of Comm failures? 

yes


[2012-06-15 15:03:26] Pool 0 slow/down or URL or credentials invalid
[2012-06-15 15:03:26] Unable to get work from pool 0 http://gpumax.com:8332

double checked credentials - still no love

I checked my back-up pool, and it works flawlessly.  Definitly GPUmax specific. 

I've been getting 7-10% rejects when connected to my private pool through GPUMAX since the updates.

I have noticed this as well

[trouserless]

Anyone else just getting tons of Comm failures?  

yes


[2012-06-15 15:03:26] Pool 0 slow/down or URL or credentials invalid
[2012-06-15 15:03:26] Unable to get work from pool 0 http://gpumax.com:8332

double checked credentials - still no love

this is my FAIL - my private pool is being DDOSed...and it was also my backup pool - very short sighted on my part.

added a real backup pool and all is working fine (not sure about rejects yet)

[boozer]

Anyone else just getting tons of Comm failures? 

yes


[2012-06-15 15:03:26] Pool 0 slow/down or URL or credentials invalid
[2012-06-15 15:03:26] Unable to get work from pool 0 http://gpumax.com:8332

double checked credentials - still no love

I checked my back-up pool, and it works flawlessly.  Definitly GPUmax specific. 

I've been getting 7-10% rejects when connected to my private pool through GPUMAX since the updates.

I have noticed this as well

Same here... rejects going through the roof... for me, it seems to occur in large bursts of rejects all at once... then its fine for awhile, then large burst of rejects again... I'll keep checking to see if it continues that way.

[yochdog]

Anyone else just getting tons of Comm failures? 

yes


[2012-06-15 15:03:26] Pool 0 slow/down or URL or credentials invalid
[2012-06-15 15:03:26] Unable to get work from pool 0 http://gpumax.com:8332

double checked credentials - still no love

I checked my back-up pool, and it works flawlessly.  Definitly GPUmax specific. 

I've been getting 7-10% rejects when connected to my private pool through GPUMAX since the updates.

I have noticed this as well

Same here... rejects going through the roof... for me, it seems to occur in large bursts of rejects all at once... then its fine for awhile, then large burst of rejects again... I'll keep checking to see if it continues that way.

Maybe the Pirate or Zux have some advice??

[Math Man]

Anyone else just getting tons of Comm failures? 

yes


[2012-06-15 15:03:26] Pool 0 slow/down or URL or credentials invalid
[2012-06-15 15:03:26] Unable to get work from pool 0 http://gpumax.com:8332

double checked credentials - still no love

I checked my back-up pool, and it works flawlessly.  Definitly GPUmax specific. 

I've been getting 7-10% rejects when connected to my private pool through GPUMAX since the updates.

I have noticed this as well

Same here... rejects going through the roof... for me, it seems to occur in large bursts of rejects all at once... then its fine for awhile, then large burst of rejects again... I'll keep checking to see if it continues that way.

Yeah, I was getting about 8 rejected shares on each worker.  Looking at my logs, it started happening right after long polling pushed out new work.  The first time was yesterday (Thursday) at 14:30 PST.  The last time that it happened was today at 12:04 PST.  If that is helpful to Pirate, good.  Otherwise, I'm just shouting into the wind. 

[cncguru]

Only have .457% rejects from home pool thru GPUMAX here but haven't gotten any public work for last 10hrs.

[yochdog]

I am pushing 3% rejects now since the upgrade....

[TheHarbinger]

I am pushing 3% rejects now since the upgrade....

About the same here.  Another reason I would like to be able to not have a backup pool on GPUMax.  That one extra hop in servers.

[naima53]

I no receive automatic payments .. What could be wrong? Who Does anyone have similar problems?

[BitMinerN8]

I no receive automatic payments .. What could be wrong? Who Does anyone have similar problems?

IRC #gpumax chan on freenode still has the topic of: "Down for maintenance. Payments for 6/14 sent at 10:12 AM CST on 6/14"

So maybe they are still working on it. 

[TheHarbinger]

I no receive automatic payments .. What could be wrong? Who Does anyone have similar problems?

IRC #gpumax chan on freenode still has the topic of: "Down for maintenance. Payments for 6/14 sent at 10:12 AM CST on 6/14"

So maybe they are still working on it. 

I don't think there was any leased work in the last day or so.  They are doing some work on the site, and probably best not to push any work until everything gets finished and works smoothly.

[nedbert9]

I no receive automatic payments .. What could be wrong? Who Does anyone have similar problems?

IRC #gpumax chan on freenode still has the topic of: "Down for maintenance. Payments for 6/14 sent at 10:12 AM CST on 6/14"

So maybe they are still working on it. 

I don't think there was any leased work in the last day or so.  They are doing some work on the site, and probably best not to push any work until everything gets finished and works smoothly.

I've been seeing sub-second pool disconnects over the past couple of days.

Also, my hash rate is ~ 5% lower from gpumax to the private pool.

Going to run directly on the private pool for now.

[phantitox]

my miners dont connect to gpumax, anyone else got this problem?

[martychubbs]

my miners dont connect to gpumax, anyone else got this problem?

+1