Official eMule-Board: Testing Version 0.51A - Official eMule-Board

Jump to content


  • (3 Pages)
  • +
  • 1
  • 2
  • 3

Testing Version 0.51A Continued unofficial development

#41 User is offline   fox88 

  • Golden eMule
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 4543
  • Joined: 13-May 07

Posted 26 June 2018 - 09:43 PM

View PostCoool, on 26 June 2018 - 08:55 PM, said:

  • Tried search Playboy found nothing using Using Search Automatic, Server and Global (Servers). Posted Image
  • Switching Categories (lot of files), lost currently downloading files list and starts downloading other files. (Slow CPU for todays standarts)
  • How about Multi CPU support (seeing only one core using)!

Are you sure your configuration is good and correct?
  • Searching for "playboy": Automatic - 300, Server - 309, Global - 309, KAD - 300. Sometimes More button was active.
  • Please explain in details what happens with categories and downloads.
  • Here typical CPU load is below 1%, and threads should be able to use different cores.

0

#42 User is offline   Coool 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 6
  • Joined: 25-June 18

Posted 26 June 2018 - 10:56 PM

fox88,
  • Transfers contains ~5000 downloads in All tab. When you choose any your made category eMule relists all files. It's so intensive on slow CPU what eMule on some seconds become Not Responding. When list is relisted, all downloads before gone and starts new downloads. At that moment and all time only one core is fully loaded. Where is Multi CPU support!

This post has been edited by Coool: 26 June 2018 - 10:58 PM

0

#43 User is offline   fox88 

  • Golden eMule
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 4543
  • Joined: 13-May 07

Posted 27 June 2018 - 07:15 AM

A practical rule is to keep the total number of uploads and downloads below 500-1000.
5000 is a serious overload, exceeding certain network limits.
0

#44 User is offline   Coool 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 6
  • Joined: 25-June 18

Posted 29 June 2018 - 10:27 AM

fox88, Search is working. Something wrong gone with server connection and network. Reconnected to server and rebooted network devices. :thumbup:
0

#45 User is offline   nephtys59 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 11-January 03

Posted 08 July 2018 - 09:34 AM

Hi, the beta 10 solved the freeze issue on "clear completed" but sometimes crashes unexpectedly.
This is the last dump I have, the previous was 0 kb : https://www.dropbox....035348.dmp?dl=0
Hope it helps.
0

#46 User is offline   fox88 

  • Golden eMule
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 4543
  • Joined: 13-May 07

Posted 08 July 2018 - 03:12 PM

nephtys59, thanks for the report.

Yours would be the third known case of random crashes in Windows 7 caused by heap corruption.
In tests, the same executable with the same settings had been running well in Windows 10.
Or in the same Windows 7, but with overlapped sockets disabled.
Therefore, that is assumed to be the Windows 7 issue, that never would get fixed by MS.
It took a while to figure out that overlapped sockets in Windows 7 could be unreliable (possibly on multicore CPU).

A workaround for Windows 7 was disabling overlapped sockets.
For that, preferences.ini file should have in [eMule] section the line:
OverlappedSockets=0

0

#47 User is offline   vivaerbetis 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 1
  • Joined: 17-June 06

Posted 10 July 2018 - 12:53 PM

Thank you fox88 for your work!

I was using amule under Ubuntu but its really unestable (too much crashes) so I migrated to emule under wine (win xp). I'm currently using your beta 10 with no problems so far.

Best regards.
0

#48 User is offline   Soul--Reaver 

  • Member
  • PipPip
  • Group: Members
  • Posts: 35
  • Joined: 15-February 03

Posted 14 July 2018 - 03:22 AM

Installed 0.51a-beta10 (was running 0.50b-BETA1)

The first thing it did was rehash around half of my shared files.
First part of the log looks like this.

Quote

14-7-2018 05:05:21: Found XXX known shared files, going to hash XXX new files
14-7-2018 05:05:21: Credit file loaded, 18819 clients are known, 77 clients deleted (not seen within 5 month)
14-7-2018 05:05:23: 196671 IP filters loaded
14-7-2018 05:05:24: Web Interface: enabled
14-7-2018 05:05:25: Hashing file: "XXXXX"
14-7-2018 05:05:26: 14 servers in server.met found
14-7-2018 05:05:26: 0 servers added, 8 not added (already listed/invalid)
14-7-2018 05:05:26: Hashing file: "XXXXX"
14-7-2018 05:05:26: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:26: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:26: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:26: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:26: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:26: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:26: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:27: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:27: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:27: Warning: XXXXX (XXXXX) might be corrupted, performing rehash of completed parts
14-7-2018 05:05:28: Found XXX part files
14-7-2018 05:05:28: eMule Version 0.51a ready
14-7-2018 05:05:28: Connecting
14-7-2018 05:05:28: Connecting to XXXXX (XXXXX - using Protocol Obfuscation) ...
14-7-2018 05:05:28: Read 200 contacts from file.
14-7-2018 05:05:28: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:29: Connected to XXXXX (XXXXX), sending login request
14-7-2018 05:05:29: Obfuscated connection established on: XXXXX (XXXXX)
14-7-2018 05:05:29: New client ID is XXXXX
14-7-2018 05:05:30: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:30: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:35: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:35: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:39: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:40: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:41: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:42: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:43: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:44: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:45: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:46: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:47: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:48: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:49: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:50: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:51: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:52: Hashing file: "XXXXX" "XXXXX"
14-7-2018 05:05:53: Finished rehashing XXXXX, file seems to be ok
14-7-2018 05:05:54: Hashing file: "XXXXX"
14-7-2018 05:05:55: Hashing file: "XXXXX"
14-7-2018 05:05:56: Hashing file: "XXXXX"
14-7-2018 05:05:57: Hashing file: "XXXXX"
14-7-2018 05:05:58: Hashing file: "XXXXX"
14-7-2018 05:05:59: Hashing file: "XXXXX"

etc.

Don't know if thats normal but thought i would at least post it to check

This post has been edited by Soul--Reaver: 14 July 2018 - 03:39 AM

0

#49 User is offline   Soul--Reaver 

  • Member
  • PipPip
  • Group: Members
  • Posts: 35
  • Joined: 15-February 03

Posted 14 July 2018 - 03:39 AM

View PostAxl, on 15 May 2018 - 01:49 PM, said:

The 0.51A version works very well....running for weeks 24/7 and I didn't find a single bug.

I have a question about development (not really a feature request, just a clarification): now in 2018, is it safe to run emule 24/7 with a SSD?
In the past there were a lot of warnings regarding the P2P programs that could short the SSDs life.

Are there still valid or the better technology of the new SSDs minimizes the risks so much that in real life we can use emule with SSD without stress?
A bigger File Buffer size (10 MB or more) and other dev optimizations could make emule more SSD friendly?

I already use a SSD for the SO+programs and an HD for Temp and downloads folders but the interesting prices of the new SSDs are encouraging me to upgrade (I have a laptop and I removed the optical unit in order to install the HDD, if I buy a bigger SSD I would reinstall the optical unit...).


eMule is unfriendly for SSD's if you have it running for multiple years and have some large config files
known2_64.met is relatively friendly since changes are only written to the end of it
known.met is unfriendly because any change causes this file to completely rewritten which happens quite often.

I once had a known.met file of about 900 mb's which causes my SSD to get aroud 20 GB's of writes a day. Luckily its smaller these days. Might have been 0.50b-BETA1 that decreased the size
0

#50 User is offline   fox88 

  • Golden eMule
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 4543
  • Joined: 13-May 07

Posted 14 July 2018 - 09:20 AM

View PostSoul--Reaver, on 14 July 2018 - 06:22 AM, said:

The first thing it did was rehash around half of my shared files.

This rehashing is caused by difference in file timestamp calculations.
Previous versions used stat kind of library functions to get file timestamp as local time.
eMule 0.51a gets file timestamp in UTC, directly from Windows API; no changes are expected here, and thus no further rehashings.

View PostSoul--Reaver, on 14 July 2018 - 06:39 AM, said:

known2_64.met is relatively friendly since changes are only written to the end of it
known.met is unfriendly because any change causes this file to completely rewritten which happens quite often.

I once had a known.met file of about 900 mb's which causes my SSD to get aroud 20 GB's of writes a day. Luckily its smaller these days. Might have been 0.50b-BETA1 that decreased the size

known.met keeps basic file information, while known2_64.met is a collection of large AICH hashes.
Therefore, known2_64.met used to be the larger one. For example, 2MB and 30 MB.
Partial purging of data, introduced in 0.49c, helps to keep config files smaller.
0

#51 User is offline   Soul--Reaver 

  • Member
  • PipPip
  • Group: Members
  • Posts: 35
  • Joined: 15-February 03

Posted 14 July 2018 - 03:36 PM

I've downgraded back to 0.50b-BETA1

During the rehashing process eMule crashed multiple times. Every time after around 1.5 hours of hashing. Since i need my eMule to be stable and most crashes reported here were related to Windows 7 (i'm running windows 10 1803) i opted for the downgrade

Quote

Faulting application name: emule.exe, version: 0.51.0.10, time stamp: 0x5b315743
Faulting module name: emule.exe, version: 0.51.0.10, time stamp: 0x5b315743
Exception code: 0xc0000005
Fault offset: 0x0000bde0
Faulting process id: 0x1650
Faulting application start time: 0x01d41b3bb6256ccc
Faulting application path: C:\Program Files (x86)\eMule\emule.exe
Faulting module path: C:\Program Files (x86)\eMule\emule.exe
Report Id: eb396d75-abae-4c38-8da6-8da21f59ce26
Faulting package full name:
Faulting package-relative application ID:


Will try this again in the future after it has had some more work

This post has been edited by Soul--Reaver: 14 July 2018 - 03:37 PM

0

#52 User is offline   fox88 

  • Golden eMule
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 4543
  • Joined: 13-May 07

Posted 14 July 2018 - 08:28 PM

Soul--Reaver,
unfortunately, provided information is insufficient.

Please try to create memory dump.
Also, there might be useful data in Log and Verbose panes.
0

#53 User is offline   nephtys59 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 11-January 03

Posted Yesterday, 06:59 PM

No more crashes after adding the string "OverlappedSockets=0" to preferences.ini. Works like a charm. Thanks a lot!
0

  • Member Options

  • (3 Pages)
  • +
  • 1
  • 2
  • 3

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users