-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Using a moved object
Using a moved object may lead to an unexpected/undefined behavior. An object is used after it's moved.
/src/mongo/db/query/optimizer/rewrites/normalize_projections.cpp:123: USE_AFTER_MOVE 176530 "leftChild" is moved (indicated by "std::move(leftChild)").
/src/mongo/db/query/optimizer/rewrites/normalize_projections.cpp:128: USE_AFTER_MOVE 176530 Returning while reference parameter "leftChild" is in a moved state.
- is duplicated by
-
SERVER-110154 Coverity analysis defect 176499: Using a moved object
-
- Closed
-
-
SERVER-110156 Coverity analysis defect 176493: Using a moved object
-
- Closed
-
-
SERVER-110157 Coverity analysis defect 176490: Using a moved object
-
- Closed
-
-
SERVER-110158 Coverity analysis defect 176488: Using a moved object
-
- Closed
-
-
SERVER-110162 Coverity analysis defect 176467: Using a moved object
-
- Closed
-
-
SERVER-110163 Coverity analysis defect 176463: Using a moved object
-
- Closed
-