RoLex

Member
  • Content count

    139
  • Joined

  • Last visited

Everything posted by RoLex

  1. Released: ApexDC++ 1.3.2

    Congratulations on another release. :unsure:
  2. Good evening. So what I'm actually seeing since version 1.3.0 of ApexDC++ and version 2.40 of StrongDC++, is that "undefined" hub protocol messages become client status messages. By "undefined" I mean a protocol message that doesn't have any known syntax, such as main chat message, or doesn't start with a dollar sign. Once the client receives such a message from the hub, it simply inleads it with three asterisks and sends it further as client status message, either in status bar only, or in status bar and main chat, depending on client settings. I'm seeing those kilometer long MOTDs being pushed right into the chat status bar, aswell as all other "undefined" hub messages that come in different length and shapes from different hub softwares; Some are already inleaded by three, two or one asterisks, which does actually represent a hub status message, and definitely not a client status message, others look like NMDC main chat messages but with a missing nick, and few look exactly as every sentence in my message does. During all my time on DC, I have always known that a client status message, which is called the way it's called because it usually appears in status bar, is a client status message that should come mainly from the client. Short version of above monologue: Give us back the old school behavior of status messages, because this new one is so damn ugly. Thank you.
  3. Enable both main chat logging and status message logging, and point them both to same file. Or am I misunderstanding something here? :)
  4. Just found out something else, looks like a bug, and I assume it's related to above issue. [2010-05-01 01:34:23] *** An existing connection was forcibly closed by the remote host. [2010-05-01 01:34:23] An existing connection was forcibly closed by the remote host. [2010-05-01 01:36:31] *** Connecting to *censored*... [2010-05-01 01:36:31] Connecting to *censored*... [2010-05-01 01:36:52] *** A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [2010-05-01 01:36:52] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. This is status message logger. I guess you will have to rewrite the status message handler after all. :)
  5. Allright, then a feature request. Please make an option along with Show status messages in main chat: Don't show status messages in status bar. One kilometer long MOTD looks really bad in a status bar, and it totally flushes all other previously sent status bar messages. For instance, you can add grayed state to Show status messages in main chat checkbox, which would do exactly what I ask for. Thank you.
  6. Bump. Any opinions?
  7. [MPP 2.0] Settings corruption

    Good evening. I'm not sure where to post this bug, in Plugins section or in here, but a decision is now made. MediaPlayer plugin, 32 bit version 2.0, running with ApexDC++, 32 bit version 1.3.1, running on WinXP SP3, does something really strange to my spam strings when I close Settings window. Set all 3 fields to exactly following string: Listening to « %[title] » « %[elapsed] of %[length] at %[bitrate] » Close the plugin configuration window, close Settings window. Then reopen the plugin configuration window and look at those messed lines. Weird characters are inserted and string length is changed. Thank you.
  8. Groups in Favorite

    This issue has been known for ages, and is issued by Windows RichEdit component. As far as I remember, developers can't do anything about it, blame Microsoft Corporation. There were some old posts explaining that issue, written by BM from around 2006, on StrongDC++ forums, which I couldn't find by the way.
  9. Released: ApexDC++ 1.2.2

    ApexDC++ forever. Thank you! ;)
  10. 100% CPU Utilisation

    Got your point, I should have read changelog better. Much better this time, continuing to love Apex! Thank you Lee.
  11. Forums upgraded to IPB 3.0

    Works like a charm! Thank you. :)
  12. 100% CPU Utilisation

    How many hubs do you have opened and how many users are there in every of those hubs? What PC specifications have you got? No, haven't tried turning Windows firewall off. How would it affect the client? Client is receiving and sending data to the socket no matter if the firewall blocks it or not. What more information do you need except the one you already got here: showtopic=3264 ?
  13. Forums upgraded to IPB 3.0

    Another one with attachments; 500 KB total quota per user? How will I be able to upload attachments now and in the future? Does removing old attachments help? Not sure about importance of old attachments. :)
  14. 100% CPU Utilisation

    I have to agree with Excalibur. Today when amounts of users in my 32 hubs are high I can once again (exactly as in 1.2.0) reproduce the 100% CPU usage with 1.2.1. My previous posts about this issue: showtopic=3264 What am I going to do now? I'm forced to 1.2.1, can't go back to 1.1.0, but still got a server to run on this PC. 100% CPU usage isn't good for server applications at all.
  15. 100% CPU Utilisation

    What version of Apex?
  16. Forums upgraded to IPB 3.0

    Looks great. There is something wrong with uploading a photo though, maybe the upload directory isn't writable. Uploading a GIF file @ 3,37 KB, 100x133 px, in My account > Profile > Change photo results:
  17. Celebrating 4 million downloads

    Congratulations on 4 millions deal. :)
  18. Released: ApexDC++ 1.2.1

    Congratulations on new release, always loving Apex! :)
  19. Downtime update (back online)

    What about plugin section, are latest plugin releases still attached? It would be safer to add all plugins to SF.net download section aswell. Regards.
  20. Someone is trying to use your client to spam

    That is not a bug in ApexDC++. That message means that the hub you are logged in to is used for CTM flood, aka DDoS attack. If the operator in that hub strongly denies that it's hub issue, I'm 99% sure he is responsible for the attack. Please leave the address of that hub and I can check it out if you like.
  21. Hashing error

    Use /rebuild command to rescan shared folders and rebuild the hash database.
  22. Using a lot of CPU

    Hi. Congratulations on new release. But there is one but as always, it's exactly the same for my part, as was in beta version of 1.2.0. This new version constantly uses alot CPU, this never happens in 1.1.0. I have started the client, opened my regular 30 hubs and waiting. It takes about 15 seconds, the CPU usage is normal, about 0-5%, that is what I always have with 1.1.0. Then after those 15 seconds the CPU usage raises up to 80-90%, it holds there for about 5-8 seconds and then goes back to 0-5% of usage. Then again 15-20 seconds passes, I get exactly same thing, CPU usage raise to 80-90% and stays there for another 5-8 seconds, whereafter it goes back to normal. This is happening constantly, no matter what I do, no matter the chat activity. I should mention that there is not a single file in download queue, no searches or dowloads going on, only a single upload with regular speed of 50-60 KiB/s, and ofcourse about 25 users in waiting list for upload. When I open CMD debug window without filter I see regular NMDC protocol messages from all hubs, both incoming and outgoing, there are most mixed searches and MyINFO's, nothing special, it's not like there are 50 search or CTM requests incoming at one moment every 15 seconds. Completely normal process of 30 opened hubs. It takes me less than 1 minute to close down 1.2.0, replace the executables and open 1.1.0 with same settings, same hubs, same time, same data going through the client sockets. But 1.1.0 never has this problem with high CPU usage, there I have constant 0-5% CPU usage no matter what I do. 1.2.0 is evil. I have managed to take a screenshot with exact thread and thread stack which constantly creates the huge CPU usage using Process Explorer, it's always same thread that is created, causes the CPU usage, and is destroyed again, as you can see on the screenshot attached below. There is another screenshot with graphical CPU usage history attached, so you can see that it happens constantly. Please, what function in ApexDC++ 1.2.0 is responsible for mentioned thread? Let's find out, I'm ready to help as much as I can and I really want to know due which reason this behaviour is caused. Any answers appreciated. I'm using Windows XP Professional with final SP3 installed. Thank you.
  23. 100% CPU Utilisation

    Not really TCP connections, looks like plugin API functions to me. By the way, it looks like your Process Explorer is showing invalid values for CPU usage. 52.38 + 43.75 + 42.86 is way more than 100%. :blink:
  24. 100% CPU Utilisation

    Can this be related: http://forums.apexdc.net/index.php?showtopic=3264 ?