This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author HugeAckmen
Recipients HugeAckmen, asvetlov, yselivanov
Date 2019-12-04.18:29:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1575484189.99.0.873814899855.issue38973@roundup.psfhosted.org>
In-reply-to
Content
When accessing Shared Memory Lists, occasionally the shared memory list will have a length of zero for only one line of code.

Even know the length of the list is constant and greater than zero, when accessing this list, like say sml[0], python returns a ValueError complaining that sml is an empty list.

As well, if you print out sml on the very next line in the exception handler, then you get a full length list, with no access issues whatsoever.

This isn't a locking issue, since locks were acquired before writing to the lists, and released after writing.  This is a shared memory list runtime access consistency issue.

An Example of this Issue can be Seen Here:
https://github.com/uofrobotics/RPLidarVidStream

The issue is in the process_data function, only when smd, sma, smq, or sml are read from.
History
Date User Action Args
2019-12-04 18:29:50HugeAckmensetrecipients: + HugeAckmen, asvetlov, yselivanov
2019-12-04 18:29:49HugeAckmensetmessageid: <1575484189.99.0.873814899855.issue38973@roundup.psfhosted.org>
2019-12-04 18:29:49HugeAckmenlinkissue38973 messages
2019-12-04 18:29:49HugeAckmencreate