<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/magstripper/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/magstripper/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/magstripper/bugs/</id><updated>2007-08-20T22:46:33Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>Index out of bounds, max swipes</title><link href="https://sourceforge.net/p/magstripper/bugs/1/" rel="alternate"/><published>2007-08-20T22:46:33Z</published><updated>2007-08-20T22:46:33Z</updated><author><name>magstripper</name><uri>https://sourceforge.net/u/magstripper/</uri></author><id>https://sourceforge.netb3c7d3649d30f6a2e032fcfd4555afc4ad55dce3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;array index out of bounds 1&amp;gt;=1 exception occurs when constant swipes are being read and the cpu chokes for a short timeframe. The "1" refers to the preference of the max swipes to store. A guess is this happens because by the time all the observers are triggered to remove the swipe from the list a new swipe already exists. I am unsure exactly how to reproduce this besides just swipe the card fast with max swipes set. I don't get a good stack trace due to it being caused from an observer's update(). The app doesn't crash so it's not a huge deal.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>