Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIGABRT #4393

Open
Maxiking1365 opened this issue Sep 11, 2019 · 13 comments

Comments

@Maxiking1365
Copy link

@Maxiking1365 Maxiking1365 commented Sep 11, 2019

Client version: 1.12.2
Server OS: Linux (DebianOS)
Commit id: 7678d5e

Just playing Minecraft, Server always crashesh with SIGABRT or SIGSEV and it error like Window lost sync. (sry when im this is not so helpful im new to this all)

Here is the Output from the Console:

[23:16:12]   D:    | Cuberite has encountered an error and needs to close
[23:16:12] Kicking player Maxi for "Server shutdown"
[23:16:12] Details | SIGABRT: Server self-terminated due to an internal fault
[23:16:12] Cuberite local build build id: Unknown
[23:16:12] from commit id: approx: 7678d5e6ed6fcc9361416ef41c43fa09a1d49f6f built at: approx: 2019-09-10 12:31:09 +0100
./Cuberite(_Z15PrintStackTracev+0x14)[0x21de80]
./Cuberite[0x20e058]
/lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer+0x0)[0x76be1120]
Abgebrochen


[23:07:38] *** Window lost sync at item 0 in SlotArea with 1 items ***
[23:07:38] My item:    -1:0:0 * 0
[23:07:38] Their item: oaksapling:0 * 34
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

(formatting edited by madmaxoft)

@madmaxoft

This comment has been minimized.

Copy link
Member

@madmaxoft madmaxoft commented Sep 12, 2019

The server crashing always is strange, but lucky. Would you be willing to compile a debug version, so that there's more info about the crash?
std::bad_alloc usually means either not enough memory, or a bug asking for too much memory in the first place.

Another thing that would help would be to take note of every click you make in the UI, then refine it into a minimum example which makes the server crash.

@Maxiking1365

This comment has been minimized.

Copy link
Author

@Maxiking1365 Maxiking1365 commented Sep 12, 2019

yeah i compile a debug version, std::bad_alloc means not enough memory is possible i mean my pi 3 was a fair gift and it only has 1 GB of RAM but on the other hand the crash also appears when the server is empty.

@Maxiking1365

This comment has been minimized.

Copy link
Author

@Maxiking1365 Maxiking1365 commented Sep 14, 2019

It was pretty silent over the last days but today we wanted too play here we go again new failures with the debug version i never had before
Server Output.txt
Output2.txt

@E14

This comment has been minimized.

Copy link
Contributor

@E14 E14 commented Sep 17, 2019

Those are somewhat diverse errors, are you sure your RPi is not overheating or has faulty memory?

Could you make sure by running a memtest (reboot and select memtest from the boot menu, or boot from a live Linux that includes memtest - most of them do) and checking temps while playing?

htop should show temperatures by default on Raspbian, for slightly longer term temperature monitoring I can suggest the very lightweight netdata, it should list temps in the sensors section.

@Seadragon91

This comment has been minimized.

Copy link
Contributor

@Seadragon91 Seadragon91 commented Sep 17, 2019

@Maxiking1365 If you still can reproduce it, then please try the steps under "Live Analysis" in this cuberite forum post.

Edit: Do this steps for the debug version of cuberite

@Maxiking1365

This comment has been minimized.

Copy link
Author

@Maxiking1365 Maxiking1365 commented Sep 17, 2019

I will test everything i just need a bit of time

@Maxiking1365

This comment has been minimized.

Copy link
Author

@Maxiking1365 Maxiking1365 commented Sep 24, 2019

so i am back and done testing i`ve done severeal memtester loops with diferent amounts of RAM every run was completed without any error also the temperatures of the Pi are pretty good the highest i saw was 39,5 degrees Celsius unfortanely im not able the recreate the SIGSEV and SIGABRT errors the is in the debug version still crashing with: double free or corruption (out) or with the memory error (Speicherzugriffsfehler) on the normal release version the server simply says Server shutdown. So im running out of ideas and i will try to make everything fresh with an debian without a UI on my next days off, maybe that will help.

@madmaxoft

This comment has been minimized.

Copy link
Member

@madmaxoft madmaxoft commented Sep 25, 2019

I'm afraid I don't understand your comment enough. Did you try running Cuberite under GDB? Did it crash? Did you get a backtrace from the crash?

If memory serves well, SIGABRT can also mean an attempt to access unaligned memory (e. g. reading a 16-bit word from an odd address). These should have been eradicated from the source long ago, but perhaps we missed something?

@Maxiking1365

This comment has been minimized.

Copy link
Author

@Maxiking1365 Maxiking1365 commented Sep 25, 2019

I think i have the same issue like you i dont understand what you mean? Whats GDB?

@madmaxoft

This comment has been minimized.

Copy link
Member

@madmaxoft madmaxoft commented Sep 25, 2019

GDB is the debugger, used on Linux machines.

Did you read the forum link? It provides a step-by-step guide for what we want; feel free to ask if any of the steps are unclear.

@Maxiking1365

This comment has been minimized.

Copy link
Author

@Maxiking1365 Maxiking1365 commented Sep 25, 2019

Ohh yeah i saw that, i mean i can try that also but Like i wrote before i dont get the SIGABRT anymore, but tomorrow i try it again maybe i will find something

@Maxiking1365

This comment has been minimized.

Copy link
Author

@Maxiking1365 Maxiking1365 commented Sep 26, 2019

so now i have a crash.txt with a SIGSEGV error
crash.txt

@Maxiking1365

This comment has been minimized.

Copy link
Author

@Maxiking1365 Maxiking1365 commented Sep 26, 2019

and i got the SIGABRT but only on the release version
crash (1).txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.