When I press install a message pops up: "[sync] Child process terminated unexpectedly with code -529697949" This is the number that pops up 9/10 times.
Please help Ya Boi Tyrone
Child process terminated unexpectedly with code -529697949
Issue #138
on hold
Comments (38)
-
-
-
assigned issue to
overfl0
-
assigned issue to
-
You may want to try again with the new launcher v1.1 and check if the issue still persists: https://bitbucket.org/tacbf_launcher/tacbf_launcher/downloads/TB_Launcher.exe
-
I'm still getting this crash (and code) in v1.1. TS3 is not running when the crash occurs.
I deleted all previous settings for TBLauncher (in AppData and MyDoc) before attempting to run TBLauncher.
I have directed TBLauncher to my ArmA3 directory due to already installed mods (which I maintain using PwS at the moment). I also tried moving the required mods into a \Tactical Battlefield directory before running TBLauncher, but it still crashed.
-
The only thing I was able to find was that -529697949 is the same as 0xE06D7363 in hexadecimal, which led me to this article:
https://support.microsoft.com/en-us/kb/185294
In plain english, it means the launched program (plugin installer from TeamSpeak) has encountered an exception it has not handled (not caught). This suggests an issue with TeamSpeak itself.
What is your TS version? Try upgrading TS to the latest version and check if this solved the issue. If so, please post the faulty version number.
-
My TS3 was the latest 32bit version 30.0.19.1.
I am running Windows 7 x64, so I'm not sure if the mixture of x64 and x32 would be an issue in relation to your response. Happy to help troubleshoot as needed. Feel free to email me directly.
-
Alright! Always nice to see people actively willing to troubleshoot! Usually it's hard enough to get any reply from them for a simple question like "does this issue still persist?".
I'll see what I can do to pinpoint the issue. Will check myself with TS 32bit.
In the meantime, could you navigate to the @task_force_radio mod directory, find a file that ends with .ts3_plugin (in some subdirectory) and try to install it by double clicking on it? This should launch the TS3 plugin installer. If this succeeds, then the problem is probably on my side. Otherwise, I'm afraid I cannot do much about it and you should notify the TS3 staff.
-
- changed title to Child process terminated unexpectedly with code -529697949
-
The TFR TS3 plugin was located in: \Arma 3\@task_force_radio\TeamSpeak 3 Client\tfr.ts3_plugin
It installed with no problems. However I should add that both TS3 and TFR were already installed when I attempted this.
-
I tried to reproduce the issue on the same software as you (latest TS 32bit, win7 x86-64) without success.
However I should add that both TS3 and TFR were already installed when I attempted this.
1) Could you remove
C:\Program Files (x86)\TeamSpeak 3 Client\plugins\task_force_radio_win32.dlland try again with the original launcher, to make sure the problem shows up even when almost everything is already installed?2) Afterwards, please try this executable: https://bitbucket.org/tacbf_launcher/tacbf_launcher/downloads/TB_Launcher_madrabbit.exe Remove any file that is related to the TFR TS plugin, for example
C:\Program Files (x86)\TeamSpeak 3 Client\plugins\task_force_radio_win32.dlland launch the custom launcher.Instead of launching the TS3 installer, it will run the calculator (as admin). Tell me if it worked fine or if it threw an error. I'm trying to find what exactly is causing the error: the program being called or the method of calling the program.
You're from the USA, right? (I'm asking about the timezone)
-
I'm based in Australia and used to be part of the TacBF team til about v3.8.
1) Renamed extensions of both x64 and x86 TFR plugins to .BAK in the TS3 plugins directory then tried the original launcher v1.1 = same -529697949 crash. Note: my TS3 path is: D:\Games\TeamSpeak 3 Client\plugins. Is the TBLauncher assuming the same TS3 path for everyone?
2) Kept the TFR plugins with .BAK extensions from (1) and ran the madrabbit specific TBLauncher you provided = same -529697949 crash. There was no indication that 'the calculator' was running before or after I pressed 'Install'. New madrabbit specific TBLauncher was also asking for Windows Firewall permission and gave a different error on the second and subsequent attempts after allowing it through the firewall = -10737418719.
-
Well, I don't really have any idea on how to pinpoint the issue, to be honest. I'll maybe have to create another executable with absolutely everything being logged and then let you run that thing but this might take me some time.
Are you on TacBF's discord channel? How could I reach you directly?
-
One last question: when exactly does this message occur? I assumed this was while installing the TS plugin but might be wrong. If this error shows up after you click OK when you are informed that ts3plugin installation will be started, do you see the UAC prompt asking you to run the installer as an administrator or not?
-
Hey! I need your answer to my last question to proceed with pinpointing the source of the problem: when exactly does the error occur?
-
Hey Stacktrace I got your PM on the TacBF forums and have been too busy to retest and reply.
When I select "Install" (now "Upgrade"), I get a Windows crash notification and then the error soon after. I've never seen anything in the displayed messages from the TBLauncher to indicate that this crash was TS3 (plugin) related, and my UAC is as disabled as it can be due to annoyance, so I doubt I'd see UAC related messages. Just to reiterate, I only use the admin account on my computer.
As for direct contact, I am not on (nor have tried) Discord. However you can contact me via TacBF PM or this BitBucket issue for which I also get email notifications, and I will respond when I can.
-
Uh, oh...
Do you get any indication of a download taking place at all? Maybe it's not the TS part but the bittorrent part that throws the exception? I'm talking about the messages that are shown above the progress bar (above the FORUM button).
Could you pack the files from c:\users\<youruser>.kivy\logs and send them to me? (PM on forum if you care about privacy :). I may actually find something in there that will help me figure out what part of the code may be causing the issue. To be honest, I have not the slightest idea of what to look at...
FYI: There will be many files in .kivy\logs. I'm only interested in those few files modified in the last minutes of the crash. There should be about 4 of them.
-
I've sent you a PM in the TacBF forums with a DropBox link to zip files of the logs. - Initial testing including the 'TB_Launcher_madrabbit.exe' test on 16/06/16 - Subsequent testing about potential UAC errors on 21/06/2016
From a brief view of the contents, there doesn't seem to be any privacy issues that I need to be concerned about. However I did find the following entry which may agree with your assessment of the bittorrrent problems:
[INFO ] Autoupdater: Up to date file missing. [INFO ] Autoupdater: executable dir: D:\Games\Steam\SteamApps\common\Arma 3 [INFO ] Autoupdater: dir_is_writable: True [INFO ] InstallScreen: syncing failed [INFO ] InstallScreen: syncing failed. Enabling the install button to allow installing again. [INFO ] Base: Leaving application in progress... [INFO ] InstallScreen: Application Stop, Trying to close child process [INFO ] No open para. App can just close
-
- removed component
Hi!
Please download the following executable and run it: https://bitbucket.org/tacbf_launcher/tacbf_launcher/downloads/TB_Launcher_madrabbit_logs.exe
Send me the logs generated by this executable. The most important file should be the one that contains the "Line xxx" lines. I am tracing the file in order to find what lines have been executed and at what moment the program execution stops.
After that, I may be able to deduce what exactly the problem is... or not. Thanks for helping me! :)
-
0) First attempt at executable
1) Windwos Firewall acces prompt = allowed access
2) Crash with code -1073741819
3) Retry executable
4) Crash with code -529697949
5) Prompt for Windows Firewall appeared again = allowed access again?!
6) Retry executable
7) Crash with code -1073741819, no Window Firewall prompt on this third attempt
The following Warning in the logs is common for all three attempts. All logs zipped an link to you via TacBF forum PM.
[INFO ] Logger: Record log in C:\Users\mad rabbit\.kivy\logs\kivy_16-06-23_11.txt [INFO ] Kivy v1.8.0 [INFO ] Factory: 157 symbols loaded [DEBUG ] Cache: register <kv.lang> with limit=None, timeout=Nones [DEBUG ] Cache: register <kv.image> with limit=None, timeout=60s [DEBUG ] Cache: register <kv.atlas> with limit=None, timeout=Nones [INFO ] Image: Providers: img_tex, img_dds, img_pygame, img_gif (img_pil ignored) [DEBUG ] Cache: register <kv.texture> with limit=1000, timeout=60s [DEBUG ] Cache: register <kv.shader> with limit=1000, timeout=3600s [WARNING ] File: sync.modmanager Line 331 [WARNING ] File: sync.torrentsyncer Line 66 [WARNING ] File: sync.torrentsyncer Line 74 [WARNING ] File: sync.torrentsyncer Line 80 [WARNING ] File: sync.torrentsyncer Line 84 [WARNING ] File: sync.torrentsyncer Line 87 [WARNING ] File: sync.torrentsyncer Line 89 [WARNING ] File: sync.torrentsyncer Line 96 [WARNING ] File: sync.torrentsyncer Line 100 [WARNING ] File: sync.torrentsyncer Line 103 -
Oh well.. this is going to be a wild ride! :D
It looks like the libtorrent library is crashing when a call to listen_on() is made. This is normally used to select the port on which the program is going to listen for incoming connections. I'm suspecting a bug in libtorrent because this function is supposed to return an error value on error and nor crash the whole program :-/.
I'm going to evaluate ways to pinpoint the problem. Maybe something that will produce a core dump that I would then be able to pass to libtorrent developer if it turns out to be a real libtorrent issue.
I have no idea yet why are you getting prompted multiple times by the firewall.
In the meantime: are you using some kind of esoteric firewall or something else that might mess with establishing socket connections? Any idea why would libtorrent crash at this precise moment on your machine? If you have tried to reproduce that issue on other machines, was the outcome the same? (I can provide you with a file that will bypass some requirements like the fact that Arma or TS have to be installed).
-
Uh... Are you still there? I've investigated a way of getting crash dumps in windows and it looks like this won't be easy (for me :).
I would like to know if you're still interested in pinpointing the cause of the issue. If yes, see the steps to take below.
This will probably not work yet because it seems I will have to recompile a debug version of libtorrent to attach to the launcher for enabling the analysis. Recompilation will probably be complicated (but as long as I know you'll use it I'm willing to take the time to recompile everything - that's why I'm asking whether you still are interested).
Download this registry file and run it on your computer: https://bitbucket.org/tacbf_launcher/tacbf_launcher/raw/36dfcfa00b13b15026670cfdbedd265e9d8d7562/docs/crash_dumps_on_windows.reg
Your computer will now create crash dumps when a program crashes. They should look like this:
Copy those files and upload them somewhere. I'll try to analyze them afterwards. If that doesn't work without additional modifications, I'll probably have to recompile libtorrent, as I mentioned above.
-
@madrabbit711 Hey! Quick reminder: I would like to know whether I should prepare a debug version of libtorrent for you, in order to figure out the problem that shows on your machine.
-
- changed status to wontfix
Without anyone to reproduce the error and also willing to help running some custom executables, I'm unable to fix this issue.
If you or anyone else still have this problem, feel free to reopen this issue.
-
On holidays now, so I've got more time to play around with things like this.
I tried using TBLauncher v1.2.2 am now getting 'Child process terminated unexpectedly with code 0'.
However despite using the REG file you provided, no crash dump file was created in the default 'AppData\Local\CrashDumps' directory or the directory you specified. I even tried modifying the directory in the REG file you specified to create the dump in 'C:\TEMP\WindowsCrashDumps', but only the directory was created.
Best I could find in relation to this recent TBLauncher v1.2.2 crash was the log on Windows Event Viewer, which I've copied and uploaded here: https://www.dropbox.com/s/szvt8wgz6z07ol4/TBLauncher_v122_mrCrash_EventViewer.txt?dl=0
I also did find an old crash dump file for TBLauncher in the default directory I specified above and have uploaded it for you: https://www.dropbox.com/s/hj764pj9m9z4mte/TBLauncher.exe.7132.dmp?dl=0
-
I tried using TBLauncher v1.2.2 am now getting 'Child process terminated unexpectedly with code 0'.Wow, are you sure you have not changed anything on your computer? I mean, something related to a firewall, AV, etc... Maybe you upgraded to a new windows version?
Anyway, if you get code 0, it means the program has not crashed but terminated (more or less) normally and the issue is completely different from what we're discussing right now.
You would need to create a separate bug report for that and attach your new logs to that report if you want this solved.
Of course, since there is no crash, there will be no core dump so don't bother looking for one on your drive.
Also, thanks for the old core, but unfortunately, I have no idea what executable was used to create that core and thus I cannot use it for debugging :(. If you have the error code -529697949 again, submit your data here. Otherwise I suggest creating a separate issue.
-
Hello, I am having the same issue as the OP. Was a root cause ever found? I'm running Windows 8.1 64bit. Latest TS client, Clean install of Arma with only one Mod "Battle Royale". Tried turning off firewall and realtime protection. Uninstalled all other Torrent clients. Still getting error message.
-
@cybrnyte All we know right now is that the issue seems to happen when initializing the bittorrent part of the code.
This looks like either a bad libtorrent-python usage or a bug in libtorrent itself. This may or may not be related to some configuration quirks that you have on your computer: the firewall, the number of network cards, etc...
This has never happened on my computer so I cannot troubleshoot the problem :(. Are you willing to help finding the root cause? This would mean running the custom executables I will send to you a few times.
I'm afraid I won't really have the time to prepare them within a week, unfortunately.
-
I work in IT so would love the opportunity to help you troubleshoot. When ever you are ready just let me know. Thanks for the quick response. I'll keep digging on my end as well.
-
overfl0, Thanks for the tip. I discovered what the problem was. I use this machine for setting up network scenarios in GNS3 and VMware which require numerous virtual network adapters. I disabled all of them but the active LAN interface and ran the launcher again. This time it's syncing as it should.
Best regards and many thanks!!!
-
Wow! That's really great you got it working! I was expecting to be forced to manually compile libtorrent in debug mode to get a dump from you that I would then be able to analyse. (actually, the fact that you work in IT persuaded me to try that today and I was in the process of installing MSVC :).
One last thing: for a better world ( :) ) could you try reproducing the error by running the sample libtorrent code and checking if it crashes? You would have to install python 2.7 and python-libtorrent and then just run a simple script:
- https://www.python.org/ftp/python/2.7.11/python-2.7.11.msi
- https://github.com/arvidn/libtorrent/releases/download/libtorrent-1_0_9/python-libtorrent-1.0.9.win32.msi
- https://github.com/arvidn/libtorrent/blob/master/bindings/python/simple_client.py
python simple_client.py <sometorrent.torrent>The libraries above are exactly what I'm using right now with the launcher. If even the simple_client.py crashes, it's a bug that should be reported to libtorrent's creator, because that will also help other people that are having the same error in the future. FYI: the error should occur during the
ses.listen_on()call.If you can pinpoint what exactly caused the error, I will add a custom error message to the one you've been seeing so that people know how they can fix their issue.
-
@madrabbit711 In case you're not following this thread and you would try playing TacBF or Frontline, @cybrnyte has found the cause of the error you've been seeing.
-
@overfl0 , I've been able to replicate the issue in a couple of ways.
First some background info. I have 11 network adapters 2 physical and 9 virtual. Of the virtual adapters there are 2 loopbacks, 1 virtual from Virtualbox and 6 from Vmware.
With only 1 physical adapter enabled I'm able to run the simple_client.py and start downloading a torrent. I then started enabling adapters one at at time. I started with the loopbacks then moved to the virtuals installed by VirtualBox and Vmware. Once I got to the 7th adapter I could no longer run the simple_client and the tacbf_launcher that was running while I was performing my tests terminated. As soon as I disabled the 7th adapter and ran the simple_client again it worked. I've verified that it makes no difference as to which adapters are enabled it always errors out when the 7th adapter is enabled.
Here is the output of the script stepping through via pdb:
c:\Users\cybrnyte\Desktop>python -m pdb simple_client.py nas.torrent
c:\users\cybrnyte\desktop\simple_client.py(5)<module>() -> from future import print_function (Pdb) n c:\users\cybrnyte\desktop\simple_client.py(7)<module>() -> import libtorrent as lt (Pdb) n c:\users\cybrnyte\desktop\simple_client.py(8)<module>() -> import time (Pdb) n c:\users\cybrnyte\desktop\simple_client.py(9)<module>() -> import sys (Pdb) n c:\users\cybrnyte\desktop\simple_client.py(14)<module>() -> ses = lt.session() (Pdb) n c:\users\cybrnyte\desktop\simple_client.py(15)<module>() -> ses.listen_on(6881, 6891) (Pdb) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
-
Yup, you're right, I've just confirmed this myself. I created 6 VirtualBox Host-only Adapters and the launcher started crashing.
I've disabled (not removed!) my only physical adapter and only kept the 6 VB adapters enabled and the launcher was working again. After adding a 7th VB adapter - it crashed. This looks like there is a hardcoded value of 6 somewhere, and it definitely isn't in my code. Whew! :)
Thank you very much! You've saved me many hours of compiling and debugging :)
Also, I've tested the same thing on linux, with virtualbox interfaces, but with
libtorrent 0.16.18(that old, unfortunately) but was unable to reproduce it.I was unable to reproduce it with a newer distribution that had
1.0.7as well, but there I was forced to use network card aliases (eth0:x) instead as this was a cloud VM so I'm not sure if this counts.This is something that should be reported to libtorrent ( https://github.com/arvidn/libtorrent/issues ). Do you want to be famous? :) Otherwise, I can report that myself if you're not interested.
Thanks again!
-
Now that I'm looking through the issues already submitted, this might be this issue: https://github.com/arvidn/libtorrent/issues/843
However, I think it would be better to play it safe and create a new issue while notifying that they may be related.
-
Your googlefoo is better than mine. :) I was searching for libtorrent issues with multiple adapters enabled in windows and wasn't successful. I checked out that ipconfig.txt file from the article you posted and it sure would appear that they are falling prey to the same issue. In some fashion at least.
As far as being famous...I'll pass. :) Feel free to submit it because you'll be able talk to it much more intelligently than this hack can.
I'm grateful to folks like you and the community for putting your time in on projects like Tactical Battlefield Launcher/Installer and anything I can do to contribute makes me happy.
Have a good one and keep up the great work.
-
I not actively following but I get notifications for this issue. However this issue has never been too much of a concern for me as I just usual the manual method or PwS when I'm particularly lazy. From 'cybrnyte' responses, I doubt I would've been able to investigate to that level and/or further than I did anyway. Good to hear it's a least been identified.
-
https://github.com/arvidn/libtorrent/issues/1167
Now we wait :).
-
- changed status to on hold
- Log in to comment
Umm... sorry. Somehow I did not see any notification of your issue.
1) Try updating your teamspeak installation to the latest version.
2) Ensure teamspeak is turned off while the update takes place.
Please tell me if this fixed the issue. Again, sorry for the late reply.