Issue information
-
#000082
-
Completed
-
1.4.0
-
1.4.1
Issue Confirmations
-
Yes (0)No (0)
1
Apexdc 1.4.0 hangs if after connecting to 8 hubs(on autoconnect on startup) I select the first tab(which is my hub), program going in "Non responding" state.
If I disable autoconnect on startup and connect only to my hub, Apex hangs.Every other hub is working ok.
Did not have this issue with previous versions of Apex.
LE: Scratch that, it did same thing on another hub after ~15 min uptime.
Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: ApexDC-x64.exe Application Version: 0.7.6.0 Application Timestamp: 4d6c4d43 Hang Signature: ab66 Hang Type: 0 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Hang Signature 1: ab66e2893b8ac80d60db2879c45c3438 Additional Hang Signature 2: 9d4f Additional Hang Signature 3: 9d4f4f34686dbad449e41f3f45ce2e66 Additional Hang Signature 4: ab66 Additional Hang Signature 5: ab66e2893b8ac80d60db2879c45c3438 Additional Hang Signature 6: 9d4f Additional Hang Signature 7: 9d4f4f34686dbad449e41f3f45ce2e66
If I disable autoconnect on startup and connect only to my hub, Apex hangs.Every other hub is working ok.
Did not have this issue with previous versions of Apex.
LE: Scratch that, it did same thing on another hub after ~15 min uptime.
Is the hub running ProkaX? I have the very same problem on one such hub...
+1
Also apexdc 1.4.0 hangs when I'm press the search button two times.
And also it hangs when downloading or uploading files.
So, 1.4.0 doesn't work.
Also apexdc 1.4.0 hangs when I'm press the search button two times.
And also it hangs when downloading or uploading files.
So, 1.4.0 doesn't work.
@ Mek No, first time it was with a Flexhub tab, the one after 15 min was with a Verlihub tab so I don't think its hubsoft the reason.
Same on DB Hub, ApexDC 1.4 hangs in 100% connections to it on startup.
Edit. Not only on startup, always.
Edit. Not only on startup, always.
Ok, first question is... can anyone confirm whether this happens only with the x64 build or both 32bit and 64bit builds.
For me, the 32bit build freezes immediately upon opening and connecting to the auto-connect hubs. The 64bit build freezes on switching to a particular hub tab (ptokax, address sent via PM to Lee and Crise).
//edit: now even the 64bit build froze like the 32bit did. I edited the favorites.xml file and tried connecting to the hubs one by one. The first hub (verlihub) connected fine, the second one (verlihub too) connected, loaded the MOTD and froze with empty userlist.
I realised that when Apex freezes, there is high CPU load (over 50%).
//edit: now even the 64bit build froze like the 32bit did. I edited the favorites.xml file and tried connecting to the hubs one by one. The first hub (verlihub) connected fine, the second one (verlihub too) connected, loaded the MOTD and froze with empty userlist.
I realised that when Apex freezes, there is high CPU load (over 50%).
Agree with Mek, on freeze my Apexdc process is using ~50% of processor usage.(i have a c2duo)
Working towards a solution...
errrm... no, the problem remains 
I have this problem, too. It hangs when searching.
Anybody can provide a hub address to Crise (so he can check it out) where it hangs on connecting? I have one but it's private
Mek, on 02 March 2011 - 09:45 PM, said:
Anybody can provide a hub address to Crise (so he can check it out) where it hangs on connecting? I have one but it's private
Old Indian already sent me one address where he had hang like this, and for me everything was fine on that hub... that said if anyone has more addresses for me to checkout by all means send them.
Try downloading the latest GeoIP countrycode from Help menu. I had issues where an old countrycode database would crash the program.
Try a fresh install with slim package and see if the crash occurs.
Try a fresh install with slim package and see if the crash occurs.
Whoa... I tried fresh slim install as Lee suggested and it hangs no more. I don't understand but will keep looking.
WAAA! GOT IT! It is caused by the new GeoIP CSV file I downloaded today when upgrading Apex! However, 1.3.9 is working fine with it.
WAAA! GOT IT! It is caused by the new GeoIP CSV file I downloaded today when upgrading Apex! However, 1.3.9 is working fine with it.
I was having the same problem while connecting the public DC Dev hub with ApexDC++ v1.4.0 x64. I deleted the GeoIPCountryWhois.csv file out of C:/Program Files/ApexDC++/ and now it works fine.
Mek, on 02 March 2011 - 09:19 PM, said:
Whoa... I tried fresh slim install as Lee suggested and it hangs no more. I don't understand but will keep looking.
All fresh installs come with the latest GeoIPCountryWhois.csv but it won't overwrite an existing copy when upgrading. This bug will be fixed in 1.4.1.
Thanks for the reports!
The strange thing is, that it hangs with the newest GeoIP file.
Updating severity to: 4 - High
Updating status to: Confirmed
Updating version to: 1.4.0
Updating status to: Confirmed
Updating version to: 1.4.0
I did not do a fresh instal, just downloaded the .csv from Help>GeoIP update and replaced the old one, no hangs yet.
Thanks, good thing its not a bigger problem.
Thanks, good thing its not a bigger problem.
I stopped the problem , simply by deleting the geoip file, I tried this after updating the file and having the same results. It stopped the issue and I was able to log with no hangups.
0 user(s) are reading this issue
0 members, 0 guests, 0 anonymous users
