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

Core dump when run multiple in stream mode #4

Closed
etemiz opened this issue Jan 11, 2023 · 2 comments
Closed

Core dump when run multiple in stream mode #4

etemiz opened this issue Jan 11, 2023 · 2 comments

Comments

@etemiz
Copy link

etemiz commented Jan 11, 2023

I am collecting events from relays by running multiple instances of strfry in stream mode and this happens like in every few hours.

terminate called after throwing an instance of 'std::runtime_error'
what(): duplicate insert into Event

Loguru caught a signal: SIGABRT
Stack trace:
13 0x7f3c179f0a00 /lib/x86_64-linux-gnu/libc.so.6(+0x126a00) [0x7f3c179f0a00]
12 0x7f3c1795eb43 /lib/x86_64-linux-gnu/libc.so.6(+0x94b43) [0x7f3c1795eb43]
11 0x7f3c17cd52b3 /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc2b3) [0x7f3c17cd52b3]
10 0x5639ff8e37c3 ./strfry(+0x2b97c3) [0x5639ff8e37c3]
9 0x5639ff8e3110 ./strfry(+0x2b9110) [0x5639ff8e3110]
8 0x5639ff64d76d ./strfry(+0x2376d) [0x5639ff64d76d]
7 0x7f3c17ca7518 /lib/x86_64-linux-gnu/libstdc++.so.6(+0xae518) [0x7f3c17ca7518]
6 0x7f3c17ca72b7 /lib/x86_64-linux-gnu/libstdc++.so.6(+0xae2b7) [0x7f3c17ca72b7]
5 0x7f3c17ca724c /lib/x86_64-linux-gnu/libstdc++.so.6(+0xae24c) [0x7f3c17ca724c]
4 0x7f3c17c9bbbe /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa2bbe) [0x7f3c17c9bbbe]
3 0x7f3c178f27f3 abort + 211
2 0x7f3c1790c476 raise + 22
1 0x7f3c17960a7c pthread_kill + 300
0 0x7f3c1790c520 /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7f3c1790c520]
2023-01-11 08:15:48.106 (2499.091s) [Writer ]FATL| Signal: SIGABRT
Aborted (core dumped)

@hoytech
Copy link
Owner

hoytech commented Jan 11, 2023

Wow, thanks for your early testing! I'm looking into this now.

@hoytech
Copy link
Owner

hoytech commented Jan 11, 2023

If you do a git pull && make, I think the latest version should be fixed.

Thanks for the report!

@hoytech hoytech mentioned this issue Jan 11, 2023
@hoytech hoytech closed this as completed Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants