aMule Bug Tracker - aMule
View Issue Details
0000489aMuleMessagespublic2005-06-21 19:452005-11-01 19:25
conde_lnx 
Xaignar 
normalblockalways
resolvedfixed 
SVN 
SVN 
0000489: Infinite loop write the log "Error in CClientUDPSocket: 4"
After that amule run two or three hours, it begins to write in the file .xsession-errors this line: "Error in CClientUDPSocket: 4".
The program writes it one and another time, and the size of the file .xssession-errors grows until the hard disk is complete. Then, as the free disk is equal to zero, amule is blocked and I has to kill it with the -9 signal.

Sorry for my words, but my english is very bad.
System:
Debian testing
amule CVS (debian repository)
No tags attached.
Issue History
2005-06-21 19:45conde_lnxNew Issue
2005-06-25 16:13XaignarStatusnew => assigned
2005-06-25 16:13XaignarAssigned To => Xaignar
2005-06-25 16:16XaignarNote Added: 0001104
2005-06-26 15:35conde_lnxNote Added: 0001111
2005-06-26 21:26XaignarNote Added: 0001112
2005-10-30 20:37XaignarStatusassigned => resolved
2005-10-30 20:37XaignarFixed in Version => CVS
2005-10-30 20:37XaignarResolutionopen => fixed
2005-10-30 20:37XaignarNote Added: 0001383
2005-11-01 12:50conde_lnxStatusresolved => feedback
2005-11-01 12:50conde_lnxResolutionfixed => reopened
2005-11-01 12:50conde_lnxNote Added: 0001388
2005-11-01 19:25XaignarStatusfeedback => resolved
2005-11-01 19:25XaignarResolutionreopened => fixed

Notes
(0001104)
Xaignar   
2005-06-25 16:16   
I'm reasonably sure that this is because the UDP socket objects arnt thread-safe, yet we call them from multiple threads. However, I can't say why the messages gets placed in your .xsession-errors file, as they are simply printfs.
(0001111)
conde_lnx   
2005-06-26 15:35   
The messages gets placed in my .xsession-errors file because WindowMaker forwards the standard system out of the launched programs to this file.
(0001112)
Xaignar   
2005-06-26 21:26   
Ah, I see. Then I'd suggest that you start aMule from a console until we've fixed the problem.

Cheers,
 Xaignar
(0001383)
Xaignar   
2005-10-30 20:37   
I have committed a patch that should fix this issue.
Please let us know if you still have problems.

Cheers,
 Xaignar
(0001388)
conde_lnx   
2005-11-01 12:50   
It works fine, thanks