Bus Error #2457

Lucetia · 2021-11-24T23:27:41Z

Checklist

I read and understood ASF's Contributing Guidelines
I also read Setting-up and FAQ, I don't need help, this is a bug report
I don't own more than 10 accounts in total
I'm not using custom plugins
This is not a question
This is not a technical issue
This is not ASF-ui problem

ASF version

Latest stable release

ASF variant

linux-arm

Bug description

I went to load ArchSteamFarm and when I opened it up it did the usual auto-update. It then updated from version 5.1.5.2 to 5.2.0.6. After showing 100% progress and it went to restart it now gives met he error "Bus error".

Here is what the update process shows:

Expected behavior

Once the update restarted then ArchiSteamFarm resumes normal process and runs through update check again and then idles.

Actual behavior

Gives the error Bus error and then returns back to the prompt.

Steps to reproduce

Updated to newest version.

Possible reason/solution

No response

Can you help us with this bug report?

No, I don't have time, skills or willings for any of that

Full log.txt recorded during reproducing the problem

2021-11-24 15:03:23|ArchiSteamFarm-16115|INFO|ASF|InitCore() ArchiSteamFarm V5.1.5.2 (linux-arm/69618d1d-bf14-435b-ae8b-faacb901e7fd | .NET 5.0.11; raspbian.10-arm; Linux 5.10.63-v8+ #1459 SMP PREEMPT Wed Oct 6 16:42:49 BST 2021)
2021-11-24 15:03:23|ArchiSteamFarm-16115|INFO|ASF|InitCore() Copyright © 2015-2021 JustArchiNET
2021-11-24 15:03:26|ArchiSteamFarm-16115|INFO|ASF|InitPlugins() Initializing Plugins...
2021-11-24 15:03:36|ArchiSteamFarm-16115|INFO|ASF|UpdateAndRestart() ASF will automatically check for new versions every 1 day.
2021-11-24 15:03:36|ArchiSteamFarm-16115|INFO|ASF|Update() Checking for new version...
2021-11-24 15:03:43|ArchiSteamFarm-16115|INFO|ASF|Update() Local version: 5.1.5.2 | Remote version: 5.2.0.6
2021-11-24 15:03:44|ArchiSteamFarm-16115|INFO|ASF|Update() Changes since V5.1.5.3:
[!] ASF V5.2 opens a new major milestone due to significant .NET 6.0 runtime upgrade. .NET runtime upgrade brings a lot of under-the-hood changes, compatibility enhancements, performance improvements, features and bugfixes (@JustArchi @A$
Breaking: renamed commands bl, ib and iq (with add and rm) to tb, fb and fq, accordingly. This further helps unifying the terms used across ASF (@JustArchi #2368).
Breaking: functions previously marked as obsolete exposed to third-party plugins have been removed from ASF as a part of B release cycle (@JustArchi).
Breaking: ASF will now refuse to run as root user by default. See wiki entry for more details (@JustArchi).
ASF will now validate build checksum against independent remote server prior to automatically updating from GitHub (@JustArchi #2452).
ASF's internal codebase has changed dramatically in regards to various .NET 6.0 improvements that we've implemented. While those changes should not cause regressions in regards to previous usage, the scope of them is huge enough to warra$
.NET 6.0 allows further performance tweaking, we've updated high-performance-setup on the wiki to reflect that (@JustArchi).
Added osx-arm64 variant of ASF for 64-bit ARM-based (Apple silicon) OS X OSes (@JustArchi).
It's now possible to use SOCKS proxies as a WebProxy setting in ASF. Simply use socks5:// (or likewise) protocol (NET 6.0 enhancement).
Latest ASF-ui with new features, improvements and bugfixes (@MrBurrBurr).
Updated localization provided by our community (@JustArchi-ArchiBot).
Usual amount of other core improvements, optimizations and bugfixes (@JustArchi).

2021-11-24 15:03:44|ArchiSteamFarm-16115|INFO|ASF|Update() Downloading new version: 5.2.0.6 (21 MB)... While waiting, consider donating if you appreciate the work being done! :)
2021-11-24 15:03:46|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 0%...
2021-11-24 15:03:48|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 10%...
2021-11-24 15:03:49|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 20%...
2021-11-24 15:03:51|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 30%...
2021-11-24 15:03:52|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 40%...
2021-11-24 15:03:53|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 50%...
2021-11-24 15:03:55|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 60%...
2021-11-24 15:03:56|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 70%...
2021-11-24 15:03:57|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 80%...
2021-11-24 15:03:59|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 90%...
2021-11-24 15:04:00|ArchiSteamFarm-16115|DEBUG|ASF|OnProgressChanged() 100%...
2021-11-24 15:04:01|ArchiSteamFarm-16115|INFO|ASF|Update() Update process finished!
2021-11-24 15:04:01|ArchiSteamFarm-16115|INFO|ASF|RestartOrExit() Restarting...


<username>@<hostname>:~/ArchiSteamFarm $ ./ArchiSteamFarm
Bus error

Global ASF.json config file

No response

BotName.json config of all affected bot instances

No response

Additional info

No response

The text was updated successfully, but these errors were encountered:

JustArchi · 2021-11-25T12:54:31Z

This looks like a technical issue to me but I'll see if I can reproduce.

JustArchi · 2021-11-25T15:46:28Z

I don't believe this issue is related to ASF, bus error indicates a problem with the OS and/or files corruption, we couldn't reproduce this on linux-arm with raspbian included, and I don't have any indicator based on which there is anything to improve in regards to this in the auto-update functionality.

I recommend to downloaded latest pre-release (if you want to use it) and transfer config files over. If that doesn't work for you, likely there is some technical issue with your OS and/or machine, and that warrants for technical support, not ASF development itself.

Abrynos · 2021-11-25T16:01:11Z

As a sidenote, because that information is not included in the screenshot: I tried running all those combinations both as root and as a non-privileged user.

Lucetia · 2021-11-26T03:48:50Z

Thanks for taking a look at this. I did upgrade it from Raspbian 10 to 11 with the same error. Reformatted and reinstalled it with the same error.

The only way I did not get this error was by reverting back to the 5.1.5.2 version. Which it boots up tries to update again and then returns back to the Bus Error. So not sure what OS or machine error it would be with a reinstall and two different machines, but an older version working.

Right now I do have it working if I use 5.1.5.2 and turn off auto-updates.

JustArchi · 2021-11-26T09:48:33Z

@Lucetia this is a valuable information, I might be able to pinpoint which change exactly causes that and add a hack in ASF to override calling faulty method which should again make it working for you.

I'll provide you with some testing builds in a second so you can verify if possible.

JustArchi · 2021-11-26T09:57:08Z

@Lucetia I've compiled two test builds for you, download them from here: https://yko.im/TmTa.zip

Once you extract the zip file, there will be two folders, 1 and 2. First start with 1, the expectation is that it doesn't work for you, that's original code. Then try 2, I've disabled one function there I suspect might be a reason why it no longer works for you, let me know if that changes anything for you.

Both are debug builds, do not use them for anything else than testing. They don't have auto-update functionality. linux-arm variant.

Lucetia · 2021-11-26T22:11:32Z

@JustArchi Alright, so I tested the link you gave me and it's acting odd based on your description.

#1 - You said is the original code, but this one when I loaded it up and dropped my config folder in it worked perfectly fine.
#2 - This one worked perfectly fine as well.

So I went back to the release page I went to ArchiSteamFarm V5.2.0.7 marked as Pre-Release but stable. When I downloaded the ASF-linux-arm.zip variant then it would give me the Bus Error I got earlier.

I then went back through and tested a few different releases using the ASF-linux-arm.zip variant. Using only the files that came with it + Config from my running version.

Version 5.1.5.2 worked.
Version 5.1.5.3 worked.
Version 5.2.0.0 did not work and returned the Bus Error which seems to be the first version that uses .NET 6.0 code.

What is more interesting is that both #1 and #2 that you linked worked fine. Though you mention #1 shouldn't work since it is suppose to be based on the 5.2.0.7 code.

I'm not sure if any of that helps you or not and if you need anymore information let me know.

JustArchi · 2021-11-26T22:30:47Z

OK, this would hint that a problem is with single file or trimming, because I used neither in my zip file for additional compatribility, I'll have 3 new builds for you in a second to test.

JustArchi · 2021-11-26T22:40:50Z

@Lucetia I have 4 new zips for you.

https://yko.im/MVvk.zip - this one is original, the expectation it that it will just work because it's effectively the first one you tested above. We verify requirements didn't change.

https://yko.im/7u9N.zip - this one has single file publish.

https://yko.im/m8fR.zip - this one has trimming.

https://yko.im/KGPM.zip - this one has both single file publish and trimming. This is effectively official release setup.

Let me know which one works and which one doesn't.

Lucetia · 2021-12-02T05:58:30Z

Sorry it took me a bit longer to get back. Got swamped the last few days.

I ran all four versions and this was the outcome:

Worked:

Version 1 (Original). This one worked
Version 3 (Trimmed) This one worked as well

Both versions started up and let me know it was the first time running it and started initializing correctly.

Did Not Work:

Version 2 (Single File Publish) - Gave me the Bus Error
Version 4 (Single File Publish and Trim) - Gave me the Bus Error too

Looks like it is narrowed down to the changes made in the single file publish. Hopefully that helps and if you need anymore testing let me know!

JustArchi · 2021-12-02T09:38:40Z

@Lucetia Thanks for your feedback.

This looks like a bug in .NET runtime, can you set those environment variables:

export COREHOST_TRACE=1
export COREHOST_TRACEFILE=host.txt

Then launch single file publish (version 2) build again, and attach output of (hopefully generated) host.txt file? You can also just attach the whole file of course if it's long.

JustArchi · 2021-12-02T10:25:36Z

^ The above is the important part, but in addition to that I also have 3 more test builds for you (that I consider as a workaround if they work):

https://yko.im/3e1z.zip - this is original one that shouldn't work, once again we just test the requirements didn't change.

https://yko.im/VL79.zip - this one forces native libs to self-extract prior to running.

https://yko.im/vkKv.zip - this one forces all libs to self-extract prior to running.

You can consider giving those few a try to see if it helped anyhow @Lucetia.

Lucetia · 2021-12-02T10:55:43Z

Here's the information it gave me in the host.txt file. I'll run the three additional builds tomorrow as it is late here, but I wanted to post at least this. The file has the same as what I pasted, but just in case the file helps make it easier I added it.

I didn't see anything that might be on my end, but it is possible? If there's something I'm missing just let me know.

Tracing enabled @ Thu Dec  2 10:52:21 2021 GMT
--- Invoked apphost [version: static, commit hash: static] main = {
./ArchiSteamFarm
}
The managed DLL bound to this executable is: 'ArchiSteamFarm.dll'
Detected Single-File app bundle
Using internal fxr
Invoking fx resolver [/home/pi/ArchiS2/] hostfxr_main_bundle_startupinfo
Host path: [/home/pi/ArchiS2/ArchiSteamFarm]
Dotnet path: [/home/pi/ArchiS2/]
App path: [/home/pi/ArchiS2/ArchiSteamFarm.dll]
Bundle Header Offset: [18f0a400]
--- Invoked hostfxr_main_bundle_startupinfo [commit hash: static]
Mapped application bundle
Unmapped application bundle
Single-File bundle details:
DepsJson Offset:[1d938] Size[61fa2b8]
RuntimeConfigJson Offset:[2b0] Size[75b0f0]
.net core 3 compatibility mode: [No]
--- Executing in a native executable mode...
Using dotnet root path [/home/pi/ArchiS2/]
App runtimeconfig.json from [/home/pi/ArchiS2/ArchiSteamFarm.dll]
Runtime config is cfg=/home/pi/ArchiS2/ArchiSteamFarm.runtimeconfig.json dev=/home/pi/ArchiS2/ArchiSteamFarm.runtimeconfig.dev.json
Attempting to read runtime config: /home/pi/ArchiS2/ArchiSteamFarm.runtimeconfig.json
Attempting to read dev runtime config: /home/pi/ArchiS2/ArchiSteamFarm.runtimeconfig.dev.json
Mapped bundle for [/home/pi/ArchiS2/ArchiSteamFarm.runtimeconfig.json]
Unmapped application bundle
Runtime config [/home/pi/ArchiS2/ArchiSteamFarm.runtimeconfig.json] is valid=[1]
Executing as a self-contained app as per config file [/home/pi/ArchiS2/ArchiSteamFarm.runtimeconfig.json]
Using internal hostpolicy
Reading from host interface version: [0x16041101:124] to initialize policy version: [0x16041101:124]
Mapped application bundle

host.txt

Lucetia · 2021-12-02T22:51:05Z

I was able to test those last 3 you listed. Running all three results in the Bus Error.

Going back through some searches and logs on the day I first got it I did notice when I went to run apt update / upgrade I did get the following message:

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'testing' to 'stable' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Not that it should have anything to do with it. The Bus Error was with both Raspbian 10 and then Raspbian 11.

I just created a new VirtualBox image using the latest Raspbian image from their website and then followed the guide to installing ASF. I installed each of the libraries and they all said Up to date except for libicu which the other versions in ( ) installed.

After doing that I then get /lib/ld-linux-armhf.so.3: No such file or directory on a fresh Raspbian 11 (Bullseye) install. So I googled and found this page: https://stackoverflow.com/questions/47787562/u-boot-lib-ld-linux-armhf-so-3-no-such-file-or-directory

Which suggested to install libc6-armhf-cross which installed that as it wasn't installed. Then I executed sudo ln -s /usr/arm-linux-gnueabihf/lib/ld-linux-armhf.so.3 /usr/lib/ld-linux-armhf.so.3 as it mentioned and then when I run it again it gives the same error. This is using the same stable release.

Not sure if any of that helps, makes it worse or if there is something I goofed up on and didn't see it.

JustArchi · 2021-12-03T00:15:28Z

You shouldn't install libc6-armhf-cross, your new error suggests that your new OS isn't based on arm anymore but arm64, and ASF has a dedicated build for that.

Doesn't change the fact that the bug with linux-arm is still here for you and I'm out of ideas what else to suggest. I've reported the issue at dotnet/runtime#62273 and I'm waiting for feedback from people that know more about this than me. Lastly, I'd appreciate if you let me know @Lucetia which Raspberry Pi model you have, as that might aid in debugging, thanks.

Until the above issue is resolved, I suggest the following:

If uname -m says aarch64 or arm64, you should be using linux-arm64 build of ASF. Only if it results armv7l you should run linux-arm.
If running linux-arm is no longer possible, until the root cause is found, I recommend running generic variant of ASF.

Running generic variant of ASF involves installing .NET Core runtime through https://dot.net/v1/dotnet-install.sh script. Simply execute ./dotnet-install.sh -c 6.0 -i /usr/share/dotnet, then link dotnet binary to bin through ln -s /usr/share/dotnet/dotnet /usr/bin/dotnet. Your dotnet --info should be operative now - launch generic variant of ASF through ArchiSteamFarm.sh script attached with generic variant of ASF.

The above is a workaround, linux-arm build should be operative, but due to the fact that I don't know the root cause of the problem here, neither I have any other workaround at hand, I don't have anything else to suggest. If more people report this issue I might decide to temporarily disable single-file publish for linux-arm, but for that I need more feedback - as much as I believe you, I don't know whether the issue comes from something specific you're running on your OS or if it's general Raspberry OS problem - we couldn't reproduce this (@Abrynos). If it's the second, and more people confirm that, I'll be more willing to temporarily modify the linux-arm build to account for that, now that we know at least a valid workaround.

In any case thanks a lot for your help @Lucetia, I'll let you know if I'll have any additional questions or stuff to test, I'd appreciate if you could keep the affected machine with the problem for at least a bit longer in case .NET guys would like additional debugging output. As of me I don't have anything else to suggest, as I pretty much exhausted my options for now (maybe I'll have something new when .NET guys suggest another workaround).

I'll keep the issue open. If by any chance you're a new visitor reading this issue and having the same problem, let us know.

JustArchi · 2021-12-04T01:02:56Z

@Lucetia .NET guys would appreciate a core dump of this issue, can you add me through some more dynamic channel like Steam or Discord so I could help you in generating one? Unless you're confident with Linux environment in which case you could provide one on your own, thanks.

Ref: dotnet/runtime#62273 (comment)

Lucetia · 2021-12-23T08:56:02Z

Sorry @JustArchi I've been swamped with things in real life and haven't had a chance to check back on this thread. Is there a preference you have on Discord or Steam (I can do either). Just with holidays coming up you or I might send a response and it takes me a bit to get back.

JustArchi · 2021-12-23T12:24:42Z

@Lucetia Add me on discord in this case: Archi#8503, perhaps we'll be able to get to the bottom of this.

Lucetia · 2021-12-23T18:08:24Z

@Lucetia Add me on discord in this case: Archi#8503, perhaps we'll be able to get to the bottom of this.

I tried adding you just now and it says Archi#8503 is not accepting friend requests. They'll have to add you to become friends. So I tried messaging you in discord and still nothing

If it helps my name is `` . I didn't want to post in the help channel letting you know and spam that up.

JustArchi · 2021-12-23T18:11:39Z

Ah right, I don't accept invites normally due to spam, thanks, added you.

JustArchi · 2022-01-05T21:11:26Z

Thanks to @janvorli and @VSadov help working on the upstream .NET issue, I have available workaround for people affected by this issue in ASF.

After evaluation, the issue seems to affect only arm32 machines with a very specific kernel CPU alignment setting.

You can verify if you're affected with cat /proc/cpu/alignment. The definition for values is:

0 - Do nothing (default behavior)
1 - Warning in kernel-log with PC and Memory-Address printed.
2 - Fixup error
3 - Warn and Fixup
4 - Send a SIGBUS to the process
5 - Send SIGBUS and output Warning

Values of 4 and 5 will cause a SIGBUS crash mentioned in the original issue. Value of 2 should be a valid workaround until the issue is addressed at dotnet/runtime#62273

Therefore, to enable a workaround, try:

echo 2 | sudo tee /proc/cpu/alignment

Or directly from root console without sudo:

echo 2 > /proc/cpu/alignment

Launching ASF after setting the value above should now succeed without any further issues.

As the fix is being worked upon in upstream issue, and considering I don't have any possibility to somehow work it around directly in the ASF code, I'll close this issue.

Thank you a lot @Lucetia for aiding me in debugging, especially for core dump that helped tackle this one down.

Lucetia added 🐛 Bug Issues marked with this label indicate unintended program behaviour that needs correction. 👀 Evaluation Issues marked with this label are currently being evaluated if they're going to be considered. labels Nov 24, 2021

JustArchi closed this as completed Nov 25, 2021

JustArchi reopened this Nov 26, 2021

JustArchi added the 🤔 Requires more info Issues marked with this label are incomplete - please provide requested details for moving forward. label Nov 26, 2021

JustArchi added 🟡 Medium priority Issues marked with this label have a priority, unless there is something even more important. and removed 🟢 Low priority Issues marked with this label are actively being worked on if nothing serious is on the list. labels Nov 26, 2021

JustArchi added 🟢 Low priority Issues marked with this label are actively being worked on if nothing serious is on the list. and removed 🟡 Medium priority Issues marked with this label have a priority, unless there is something even more important. labels Nov 27, 2021

JustArchi mentioned this issue Dec 2, 2021

Regression: Bus error when running PublishSingleFile=true .NET 6.0 app on linux-arm (Raspbian) dotnet/runtime#62273

Closed

JustArchi closed this as completed Jan 5, 2022

github-actions bot locked as resolved and limited conversation to collaborators Mar 7, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bus Error #2457

Bus Error #2457

Lucetia commented Nov 24, 2021

JustArchi commented Nov 25, 2021

JustArchi commented Nov 25, 2021 •

edited

Loading

Abrynos commented Nov 25, 2021

Lucetia commented Nov 26, 2021

JustArchi commented Nov 26, 2021

JustArchi commented Nov 26, 2021 •

edited

Loading

Lucetia commented Nov 26, 2021 •

edited

Loading

JustArchi commented Nov 26, 2021

JustArchi commented Nov 26, 2021

Lucetia commented Dec 2, 2021

JustArchi commented Dec 2, 2021 •

edited

Loading

JustArchi commented Dec 2, 2021

Lucetia commented Dec 2, 2021

Lucetia commented Dec 2, 2021

JustArchi commented Dec 3, 2021 •

edited

Loading

JustArchi commented Dec 4, 2021

Lucetia commented Dec 23, 2021

JustArchi commented Dec 23, 2021

Lucetia commented Dec 23, 2021 •

edited

Loading

JustArchi commented Dec 23, 2021

JustArchi commented Jan 5, 2022 •

edited

Loading

Bus Error #2457

Bus Error #2457

Comments

Lucetia commented Nov 24, 2021

Checklist

ASF version

ASF variant

Bug description

Expected behavior

Actual behavior

Steps to reproduce

Possible reason/solution

Can you help us with this bug report?

Full log.txt recorded during reproducing the problem

Global ASF.json config file

BotName.json config of all affected bot instances

Additional info

JustArchi commented Nov 25, 2021

JustArchi commented Nov 25, 2021 • edited Loading

Abrynos commented Nov 25, 2021

Lucetia commented Nov 26, 2021

JustArchi commented Nov 26, 2021

JustArchi commented Nov 26, 2021 • edited Loading

Lucetia commented Nov 26, 2021 • edited Loading

JustArchi commented Nov 26, 2021

JustArchi commented Nov 26, 2021

Lucetia commented Dec 2, 2021

JustArchi commented Dec 2, 2021 • edited Loading

JustArchi commented Dec 2, 2021

Lucetia commented Dec 2, 2021

Lucetia commented Dec 2, 2021

JustArchi commented Dec 3, 2021 • edited Loading

JustArchi commented Dec 4, 2021

Lucetia commented Dec 23, 2021

JustArchi commented Dec 23, 2021

Lucetia commented Dec 23, 2021 • edited Loading

JustArchi commented Dec 23, 2021

JustArchi commented Jan 5, 2022 • edited Loading

JustArchi commented Nov 25, 2021 •

edited

Loading

JustArchi commented Nov 26, 2021 •

edited

Loading

Lucetia commented Nov 26, 2021 •

edited

Loading

JustArchi commented Dec 2, 2021 •

edited

Loading

JustArchi commented Dec 3, 2021 •

edited

Loading

Lucetia commented Dec 23, 2021 •

edited

Loading

JustArchi commented Jan 5, 2022 •

edited

Loading