Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Hinoe]

Hello,

I've been using aMule as a substitution for my old client for a while now. Today, I decided it was time to make use of the Import feature, since the computer running the old client will no longer have Internet access. When using Import, aMule crashes.

Error message is as follows:

Microsoft Visual C++ Runtime Library


Runtime Error!

Program: C:\Program Files (x86)\aMule\amule.exe


This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information.

Client info: aMule 2.2.6 for Windows, official binary available on http://www.amule.org/files/download.php?file=190

OS and C++ Runtime info: Windows 7 Ultimate x64, Microsoft Visual C++ 2008 SP1 Redistributable Package (x64), and Microsoft Visual C++ 2008 SP1 Redistributable Package (x86). First package is available on http://www.microsoft.com/downloads/details.aspx?familyid=BA9257CA-337F-4B40-8C14-157CFDFFEE4E&displaylang=en and second one on http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en

Step retracing:
1) Big "Import" button
2) Add imports
3) Select folder and press enter
4) Choose whether to delete the source files (both choices have the same result)
5) Crash.

Upon pressing OK, Windows proceeds as if the program was being killed due to freezing. The system tries to think of a solution, says it can't find any, and kills the app.

Any idea what can be done? I tried the obvious: installing aMule over and repairing the Visual C++ packages. The error persists. I've done that numerous times so far, always getting the error. Other that that, aMule has run flawlessly over the past month or so.

EDIT: I just figured the following information might be relevant. I managed to notice the ed2k links are added, but also that the downloaded parts are not. That is, the file I had downloaded e.g. 30% of is added to the list but starts downloading from scratch.

Thank you for your assistance.

[GonoszTopi]

That's interesting, the importer should work in 2.2.6.

Could you please try this one? It is the same 2.2.6 version, but it uses the MinGW runtime instead of the VC++ one.

Another thing you can try is a development version (using VC++ runtime).

Actually the crash may be related to W7, 64b, anything. Are you importing from a local HDD or from a network drive?

Other that that, aMule has run flawlessly over the past month or so.

Glad to hear that.

[Stu Redman]

That's a plain crash, not a runtime related crash. Also aMule for Windows is linked statically anyway so it doesn't matter what runtime is installed. 
Just tried it and noticed no problem (both 2.2.6 and SVN). Probably related to one of your downloads I should think. Please try moving your downloads (.met and .part) one by one to a different directory and try to import that. If you can narrow it down to one download please mail me the .met file.

[GonoszTopi]

That's a plain crash, not a runtime related crash. Also aMule for Windows is linked statically anyway so it doesn't matter what runtime is installed. 

You're the Windows developer, I trust you 

[Hinoe]

Hello,

I tried the mingw version as suggested; it installed beautifully, but failed to start altogether. I noticed Process Explorer would show Windows Problem Reporting (C:\Windows\SysWOW64\WerFault.exe) popping up whenever I tried to make it run. That same process pops up when the VC++ version crashes, and some basic googling shows it is as the name reports: a crash reporter.

I also tried the latest development compile available in the address you linked; it crashed just like the VC++ 2.2.6 version does when I run the importer.

I finally tried moving a few downloads to different folders and adding them one by one. Whenever I would add a download, whatever one I tried, it would crash, as long as it was not already in the download list. Sure, I can add all downloads one by one, but that's going to be somewhat annoying as I have many, not to mention I will lose all the parts I have already grabbed (seeing most files are somewhat rare).

Finally, I'm importing from a local HDD.

Thank you again. Hopefully I'll be able to help you pinpoint the location of the problem.

[GonoszTopi]

I need to know what is your "old client", to know what type of downloads you're trying to import.

Edit: And possibly its version.

[Hinoe]

Hi,

I used to use Dreamule 3.2.  From Wikipedia:

DreaMule is a peer-to-peer file-sharing free software based on eMule and eMule Xtreme. It brings new resources and facilities to the original version. This project is led by Brazilian programmer Bruno Cabral. It's an open source project, under the free GPL license, available for Microsoft Windows. An older version 3.1 has also been released for Linux.

In my opinion, it is a crappy client. It feels like an eMule "hack", and has ads in spite of claiming to be ad-free. I have wanted to move from it since not too long after starting to use it. Do notice you kind of need to understand Portuguese to work your way around the app completely, since the English translations are not exactly good. Since it is opensource, though, I guess you /can/ look up the code if you feel that will say a word or two about the files. Source is available on http://sourceforge.net/projects/pootzmod/

I'm starting to think the .met files might be somehow or other "corrupted", as in, using non-standard encoding that is causing aMule to crash. If that is the problem, I can get new ed2k links for all transfers. My main problem would be making aMule recognize the parts already downloaded; I'm not knowledgeable on how the app works, but I think it wouldn't be just overwriting the .part files.

[Stu Redman]

So - does it have .part and .met files like aMule?
Zip a few (5) of the mets and mail them to me please (sturedman at amule.org). I'd like to see if I can reproduce the problem.

[Hinoe]

Hello,

I just sent an email from the same address I have used to register here, with a zip file attached as asked.

[Vollstrecker]

Dumb question, but what happens if you just set you incoming-dir to the folder the old met's are in?

[GonoszTopi]

Dumb question, but what happens if you just set you incoming-dir to the folder the old met's are in?

Or better, the Temp dir.

[Hinoe]

I tried that a few hours ago. It works beautifully. However, if I try to import the files from the old temp folder (the real aMule temp folder), guess what happens? It crashes.

Now, I just figured there could be a quick and dirty solution that helps me "fix" the issue from my end, even though I'm still trying to understand what the hell is going on. I just thought I can rename all my files to 200+ using massive renamers and paste them at the folder. The issue would then be "solved", as in, I would have the files imported like I wanted to . About the crashes, the issue would remain unfixed, but there being now a known workaround.

Funnily, opening the .met files in Notepad I noticed there's actually information about the .part filename in them. Now, I'm not entirely sure if just renaming them still works, and I'm afraid I might crash my downloads if I go about doing that. Can I actually do it safely?

I also tried importing files from both the current run of aMule and my old Dreamule installation in another computer, running WinXP, using the same installation binary. Also crashed. I tried the SVN compile. Crashed. When trying the MinGW compile, same problem: it wouldn't even start.

I don't understand.

[GonoszTopi]

I tried that a few hours ago. It works beautifully. However, if I try to import the files from the old temp folder (the real aMule temp folder), guess what happens? It crashes.

That means that it crashes on every import. Sad thing.

Now, I just figured there could be a quick and dirty solution that helps me "fix" the issue from my end, even though I'm still trying to understand what the hell is going on. I just thought I can rename all my files to 200+ using massive renamers and paste them at the folder. The issue would then be "solved", as in, I would have the files imported like I wanted to . About the crashes, the issue would remain unfixed, but there being now a known workaround.

Funnily, opening the .met files in Notepad I noticed there's actually information about the .part filename in them. Now, I'm not entirely sure if just renaming them still works, and I'm afraid I might crash my downloads if I go about doing that. Can I actually do it safely?

I just wanted to suggest that. You can do it safely, don't care about the .part filename in the .met file. However, a fix would be better than a workaround...

[Hinoe]

Well, it's not the perfect solution, but I guess something is better than nothing. I'll do that. Thanks

What puzzles me is that though no one has been able to reproduce my issue, I get it in the exact same flavor of errors (MinGW compile not running, VC++ compiles crashing in the same routine) in two different computers, running different Windows versions. That is weird.

[Stu Redman]

Well, I was expecting a glitch in your met files that causes aMule to trip (on any platform). But guess what - import of your met files works just fine here. Both with 10024 and 10025.
I have an idea left. Maybe the import folder is causing problems? Please copy a bunch of your temp files to a simple named folder (like c:\import , no asian characters!) and try to import that.