aMule Forum

English => en_Bugs => Topic started by: Radek on January 12, 2006, 03:15:54 PM

Title: 20060112 Win32 - [fixed] amulegui error messages on console
Post by: Radek on January 12, 2006, 03:15:54 PM

When I start amulegui.exe from MingW bash, I get a lot of error messages on the console

Quote

Connecting...
Going to event loop...
Remote GUI EC event handler
LOG: Succeeded! Connection established to aMule CVS
LOG:
LOG:  - This is aMule CVS using wxMSW v2.7.0 (Unicoded) (Snapshot: Thu Jan 12 07:02:16 CET 2006) based on eMule.
LOG:    Running on Windows XP (build 2600, Service Pack 2)
LOG:  - Visit http://www.amule.org to check if a new version is available.
LOG:
RLE_Data: decoding error. 74 bytes decoded to 70 instead of 263
RLE_Data: decoding error. 6 bytes decoded to 6 instead of 7
RLE_Data: decoding error. 1 bytes decoded to 1 instead of 30240
RLE_Data: decoding error. 8 bytes decoded to 8 instead of 17788
RLE_Data: decoding error. 1 bytes decoded to 1 instead of 12079
RLE_Data: decoding error. 1 bytes decoded to 1 instead of 12854
RLE_Data: decoding error. 1 bytes decoded to 1 instead of 25953
RLE_Data: decoding error. 1 bytes decoded to 1 instead of 68
Shutting down aMule...
aMule dialog destroyed

This time I only started the program and closed it after a few seconds without any other action.

If, however, I go to "Shared Files" and exit the program from there without any other clicks/actions, I get a memory exception. The output on console is like above, only much more of the "decoding errors". Including the "Shutting down" and "Dialog destroyed".

I will compile amulegui with debug enabled and try again.

Title: Re: 20060112 Win32 - [fixed] amulegui error messages on console
Post by: lfroen on January 13, 2006, 03:57:43 PM

This error mean error in RLE decoding (data for colored progress bar). This mean that EC is transmitting/receiving junk. As a result you will got corrupted progress bar (already reported).

Actually I have same error. Since I never saw such thing before I have to assume that someone broke something in EC/remote gui/RLE/all of them.

Title: Re: 20060112 Win32 - [fixed] amulegui error messages on console
Post by: Kry on January 13, 2006, 09:15:18 PM

Seems fixed on tomorrow's

Title: Re: 20060112 Win32 - [fixed] amulegui error messages on console
Post by: Radek on January 14, 2006, 11:49:50 AM

And fixed it is  :)

There's only one (new) error message

Code: [Select]

$ src/amulegui.exe
Connecting...
Going to event loop...
Remote GUI EC event handler
LOG: Succeeded! Connection established to aMule CVS
LOG:
LOG:  - This is aMule CVS using wxMSW v2.7.0 (Unicoded) (Snapshot: Sat Jan 14 07:02:12 CET 2006) based on eMule.
LOG:    Running on Windows XP (build 2600, Service Pack 2)
LOG:  - Visit [URL]http://www.amule.org[/URL] to check if a new version is available.
LOG:
EC error - packet received, but request fifo is empty
Shutting down aMule...
aMule dialog destroyed
But I observed that shutting down amulegui takes quite long... Sth like 30 seconds. Socket timeouts or cleaning up phase or sth?

Title: Re: 20060112 Win32 - [fixed] amulegui error messages on console
Post by: lfroen on January 15, 2006, 09:55:32 AM

Quote

EC error - packet received, but request fifo is empty

Yea, this is bug: should not happen.