You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running rqiner (Qubic miner) inside Ubuntu proot, I happen to get "bus error" on some phones. This thing happens on like 5-10% of the phones, but when it happens, it just keeps killing the process and the only way to get rid of it is to just restart the device - even reinstalling termux and everything inside it doesn't help.
Steps to reproduce the behavior.
Have a bunch of S8/S9/S10 (+) phones and keep rqiner running on them (i use my own made script to run it https://github.com/ExcaliburGO/rqiner-mobile, runs inside proot-distro ubuntu) and just wait for 24h to get this thing on some of the phones.
What is the expected behavior?
I expect there should be no bus errors at all, it's actually a weird error that should probably never happen but happens in this case for some reason
System information
Termux application version: 118
Android OS version: 12
Device model: Samsung Galaxy S8/S9/S10(+)
The text was updated successfully, but these errors were encountered:
Problem description
When running rqiner (Qubic miner) inside Ubuntu proot, I happen to get "bus error" on some phones. This thing happens on like 5-10% of the phones, but when it happens, it just keeps killing the process and the only way to get rid of it is to just restart the device - even reinstalling termux and everything inside it doesn't help.
Steps to reproduce the behavior.
Have a bunch of S8/S9/S10 (+) phones and keep rqiner running on them (i use my own made script to run it https://github.com/ExcaliburGO/rqiner-mobile, runs inside proot-distro ubuntu) and just wait for 24h to get this thing on some of the phones.
What is the expected behavior?
I expect there should be no bus errors at all, it's actually a weird error that should probably never happen but happens in this case for some reason
System information
The text was updated successfully, but these errors were encountered: