search

Andy-K-Sparklight / Ari

When will we be able to create the world again? Guess not. Netease is ruining everything.
GNU General Public License v3.0
16 stars 3 forks source link

Ari Crash During Startup #30

Closed CaveNightingale closed 1 year ago

CaveNightingale commented 1 year ago 
[src/sys/Init.cc:28] Initializing system.
[src/sys/Storage.cc:52] Loading config from /home/billy/.alicorn-ch/Main.kv
[src/sys/Schedule.cc:60] Setting up UV thread.
[src/sys/Schedule.cc:65] UV thread created.
[src/core/platform/Finder.cc:43] Configured base path as "/home/billy/.alicorn-ch"
[src/core/network/Download.cc:314] Setting up download sync service.
[src/sys/Init.cc:45] Finished system initializing.
[src/extra/mod/provider/Modrinth.cc:250] Modrinth RPC server is listening.
[src/drivers/aria2/Aria2Driver.cc:106] Starting aria2 daemon with port 6801
[src/drivers/aria2/Aria2Driver.cc:113] Successfully started aria2 daemon with pid 2978954
非法指令 (核心已转储)

Some further research is needed.

Andy-K-Sparklight commented 1 year ago

Please use a debugger like gdb to give a detailed backtrace. Also, providing more information about the os environment will help to solve this.

CaveNightingale commented 1 year ago

I haven't got any stacktrace because I am not able to reproduce this.

Device Info: Huawei CREF-16 Intel i5-12500H Ubuntu 22.10

---Original--- From: "Annie K Rarity @.> Date: Sun, Jan 29, 2023 11:31 AM To: @.>; Cc: @.**@.>; Subject: Re: [Andy-K-Sparklight/Ari] AlicornCH Crashed (Issue #30)

Please use a debugger like gdb to give a detailed backtrace. Also, providing more information about the os environment will help to solve this.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

Nana-Sakura commented 1 year ago

It was fixed in f973452f5206cfc487ce8459ba7648a19f8a3364 on macOS. I will try to revert it on GNU.

CaveNightingale commented 1 year ago

It was fixed in f973452 on macOS. I will try to revert it on GNU.

I think you are talking about #28

Andy-K-Sparklight commented 1 year ago

It might likely to happen when there is memory overwriting executable segments. But possible similar crashes haven't been reported yet.

Nana-Sakura commented 1 year ago

It didn't revert, whatever it exited normally, with sigint, or even using sigkill, for nearly hundreds of times in gdb. Fairly interesting. Info: Arch Linux AArch64

CaveNightingale commented 1 year ago

Since it's really hard to reproduce, I guess it was related to thread-safety in some way. I've found that you spawn tons of threads as worker, so I'm going to have a look there.

Andy-K-Sparklight commented 1 year ago

As there are no further reports, this issue is marked as closed.