-
Notifications
You must be signed in to change notification settings - Fork 38
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
context.GetSimUe - fatal error: concurrent map read and map write #130
Comments
Output and StacktraceInitProfile and ExecuteProfile are running in different goroutines at the same time, concurrent access occurred on context.SimUeTable
|
Thanks for reporting issue. Good to see you are exploring GNBSIM to try out 40 Profiles. I hope you find the profile support useful. I will check this. |
This issue has been stale for 30 days and will be closed in 5 days. Comment to keep it open. |
Thanks for your input, @yoursunny. I am going to bring this topic to the next TST meeting to make a decision about it. |
Need this..adding comment to avoid issue getting closed. |
Remember that we increase the number of days before an issue/PR is considered as "stale" from 30 to 120 (https://github.com/omec-project/gnbsim/blob/main/.github/workflows/stale.yml#L10) |
This issue has been stale for 120 days and will be closed in 15 days. Comment to keep it open. |
Need to fix it. |
This issue has been stale for 120 days and will be closed in 15 days. Comment to keep it open. |
I have a sighting of a crash in
simue/context
package when a large number of profiles are starting/running in parallel.This error only occurred once and does not reproduce reliably.
Nevertheless, I'm reporting it here so that this race condition can be reviewed.
Configuration
1 gNB, 40 UEs, 40 profiles running in parallel
The text was updated successfully, but these errors were encountered: