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
Memory problem in CSCTriggerPrimitivesProducer #25200
Comments
A new Issue was created by @Dr15Jones Chris Jones. @davidlange6, @Dr15Jones, @smuzaffar, @fabiocos, @kpedro88 can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
I rebuild the code using debug and reran the ASAN job for workflow 11626.0
ASAN says the memory was deleted here
which as much as I can tell has no connection what so ever to the other code. |
The problem happens here
where mymap is a std::vector
So I'm guessing the value of clct.getKeyStrip() is way outside of the size of the std::vector .
|
assign l1 |
@dildick can you take a look |
@kpedro88 @Dr15Jones I'll look into it this week. |
My colleague Tao ((@tahuang1991) may have a solution. tahuang1991@20194b6. It seems the problem may be due to the fact that in recent pull requests we undid the decoupling of ME1a and ME1b in the CSC local trigger. In the Trigger & DAQ systems ME1a is seen as an extension of ME1b (and this will not change in the future). The ME1a half-strip numbering starts where ME1b ends. Thus a correction needs to be made when looking up the corresponding GEM pad number for half-strips in ME1a. The fix has yet to be tested though. |
Ping |
In previous Sven's thread, tahuang1991@20194b6 |
We are waiting for the l2s for l1 to sign off on the issue. |
There still seems to be problems with the code: See With
and
|
I will look at this one during the weekend. |
I found another bug in L1Trigger/CSCTriggerPrimitives/src/CSCUpgradeMotherboard.cc and after fixing it, I repeated the test by running "running runTheMatrix.py -l 21634.0" and confirmed that the problem was solved. either Sven or I will make a pull request to cmssw today later. |
commit to fix this bug is pushed to cmssw: |
+1 |
This issue is fully signed and ready to be closed. |
The CMSSW_10_4_ASAN_X_2018-11-09-2300 release shows a 'read after delete' problem in CSCTriggerPrimitivesProducer. However, I think that it is a misclassification and instead it is proably a memory out of bounds problem.
The text was updated successfully, but these errors were encountered: