Skip to content

Conversation

@markuspf
Copy link
Member

  • Calling Length on a weak pointer object can change the length of the
    weak pointer object, because it garbage collects unused entries
    at the end of the list.
  • Hence even though we only read, we acquire a readwrite lock
  • Thanks to Chris Jefferson [email protected] for spotting this.

* Calling Length on a weak pointer object can change the length of the
  weak pointer object, because it garbage collects unused entries
  at the end of the list.
* Hence even though we only read, we acquire a readwrite lock
@mohamed-barakat mohamed-barakat added topic: HPC-GAP Issues and PRs related to HPC-GAP gapdays2015-spring Issues and PRs that arose at https://www.gapdays.de/gapdays2015-spring labels Mar 18, 2015
* As per Reimer's suggestion check for exclusive write access in
  LengthWPObj.
* If we have write access, we discard objects at the end of the
  list, otherwise we just return the stored length.
@markuspf
Copy link
Member Author

This will be solved by #78, so I am closing this one.

@markuspf markuspf closed this Mar 18, 2015
@markuspf markuspf deleted the hpcgap-fix-mapping-region-2 branch October 26, 2015 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gapdays2015-spring Issues and PRs that arose at https://www.gapdays.de/gapdays2015-spring topic: HPC-GAP Issues and PRs related to HPC-GAP

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants