-
Notifications
You must be signed in to change notification settings - Fork 67
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
OF object tracking is not thread safe #1
Labels
Comments
bsn-abat
pushed a commit
that referenced
this issue
Oct 18, 2013
Bucket flows by cookie to speed up certain flow stats requests (https://github.com/floodlight/xindigo/pull/1)
rlane
added a commit
to rlane/indigo
that referenced
this issue
Dec 13, 2013
This pulls in BigHash. * submodules/bigcode a43da15...6873964 (30): > -Werror should be disabled due to redefines inherited from Python. > Merge into master from pull request floodlight#8: Initial DHCP parsing support. (floodlight/bigcode#8) > Merge into master from pull request floodlight#6: VPI Targets (floodlight/bigcode#6) > Merge into master from pull request floodlight#7: Enhance ICMP definitions. (floodlight/bigcode#7) > Remove trailing whitespace. > Update name. > Merge into master from pull request floodlight#5: vpitool and VPI TAP interface. (floodlight/bigcode#5) > Merge into master from pull request floodlight#2: Support for LACP and LLDP Parsing (floodlight/bigcode#2) > Set ROOT. > Merge into master from pull request floodlight#1: Update module autogeneration scripts. (floodlight/bigcode#1) > Latest. > Publishing updates. > Initial. > Documentation updates. > Import from internal repository. > Initial. > Comment cleanup. > Comment cleanup. > Comment cleanup. > Comment cleanup. > Comment cleanup. > Comment cleanup. > Comment cleanup. > Import from internal repository. > Import from internal repository. > Import from internal repository. > Update README.md > Update to new repository location. > Submodules should be not updated recursively. > Update latest.
Object tracking has been removed for some time now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In general, loci code is thread safe so long as you use normal mechanisms for controlling references to specific objects. However, the debug object tracking code is not thread safe currently. If you create or destroy of objects in different threads, you are at risk of memory corruption. The easiest work around is to not enable it by ensuring that OF_OBJECT_TRACKING is not defined in your build.
The text was updated successfully, but these errors were encountered: