Possible memory error source

Is this bug reproducible? My best guess based on the backtrace is that you
somehow ended up with a very large grid (due to some error in resizing?) and
filled up memory creating all of the targets. ..but if it's not
reproducible, then there's not much we can do.

On Fri, Aug 27, 2010 at 14:51, meganbkratz <email address hidden> wrote:

> Public bug reported:
>
> I was starting my second slice, so already had a bunch of windows open
> (prot. runner, patch, data manager, analysis). I was making a grid and
> dragged it over the corner of the camera region. I may have accidently
> clicked the corner of the camera region instead. But suddenly everything
> locked up, and I got this message:
>
> Traceback (most recent call last):
> File "C:\Documents and
> Settings\Experimenters\luke\acq4\lib\devices\Scanner\ProtocolGui.py", line
> 652, in rgnChanged
> self.regeneratePoints()
> File "C:\Documents and
> Settings\Experimenters\luke\acq4\lib\devices\Scanner\ProtocolGui.py", line
> 661, in regeneratePoints
> self.generateGrid([self.pointSize*0.5, self.pointSize*0.5], [sepx,
> sepy])
> File "C:\Documents and
> Settings\Experimenters\luke\acq4\lib\devices\Scanner\ProtocolGui.py", line
> 685, in generateGrid
> self.points.append((x, y))
> MemoryError
> Camera acquisition thread has been waiting 11.081999 sec but no new frames
> have arrived; shutting down.
>
> ** Affects: acq4
> Importance: Undecided
> Status: New
>
> --
> Possible memory error source
> https://bugs.launchpad.net/bugs/625488
> You received this bug notification because you are the registrant for
> acq4.
>

Hmm, I didn't check cause I had a cell at the time. I'll check monday. What
happens if you make the camera region larger than the 512 X 512ish region?

On Fri, Aug 27, 2010 at 9:03 PM, lcampagn <email address hidden> wrote:

> Is this bug reproducible? My best guess based on the backtrace is that you
> somehow ended up with a very large grid (due to some error in resizing?)
> and
> filled up memory creating all of the targets. ..but if it's not
> reproducible, then there's not much we can do.
>
> On Fri, Aug 27, 2010 at 14:51, meganbkratz <email address hidden>
> wrote:
>
> > Public bug reported:
> >
> > I was starting my second slice, so already had a bunch of windows open
> > (prot. runner, patch, data manager, analysis). I was making a grid and
> > dragged it over the corner of the camera region. I may have accidently
> > clicked the corner of the camera region instead. But suddenly everything
> > locked up, and I got this message:
> >
> > Traceback (most recent call last):
> > File "C:\Documents and
> > Settings\Experimenters\luke\acq4\lib\devices\Scanner\ProtocolGui.py",
> line
> > 652, in rgnChanged
> > self.regeneratePoints()
> > File "C:\Documents and
> > Settings\Experimenters\luke\acq4\lib\devices\Scanner\ProtocolGui.py",
> line
> > 661, in regeneratePoints
> > self.generateGrid([self.pointSize*0.5, self.pointSize*0.5], [sepx,
> > sepy])
> > File "C:\Documents and
> > Settings\Experimenters\luke\acq4\lib\devices\Scanner\ProtocolGui.py",
> line
> > 685, in generateGrid
> > self.points.append((x, y))
> > MemoryError
> > Camera acquisition thread has been waiting 11.081999 sec but no new
> frames
> > have arrived; shutting down.
> >
> > ** Affects: acq4
> > Importance: Undecided
> > Status: New
> >
> > --
> > Possible memory error source
> > https://bugs.launchpad.net/bugs/625488
> > You received this bug notification because you are the registrant for
> > acq4.
> >
>
> --
> Possible memory error source
> https://bugs.launchpad.net/bugs/625488
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in ACQ4 Neurophysiology Acquisition System: New
>
> Bug description:
> I was starting my second slice, so already had a bunch of windows open
> (prot. runner, patch, data manager, analysis). I was making a grid and
> dragged it over the corner of the camera region. I may have accidently
> clicked the corner of the camera region instead. But suddenly everything
> locked up, and I got this message:
>
> Traceback (most recent call last):
> File "C:\Documents and
> Settings\Experimenters\luke\acq4\lib\devices\Scanner\ProtocolGui.py", line
> 652, in rgnChanged
> self.regeneratePoints()
> File "C:\Documents and
> Settings\Experimenters\luke\acq4\lib\devices\Scanner\ProtocolGui.py", line
> 661, in regeneratePoints
> self.generateGrid([self.pointSize*0.5, self.pointSize*0.5], [sepx,
> sepy])
> File "C:\Documents and
> Settings\Experimenters\luke\acq4\lib\devices\Scanner\ProtocolGui.py", line
> 685, in generateGrid
> self.points.append((x, y))
> MemoryError
> Camera acquisition thread has been waiting 11.081999 sec but no new frames
> have arrived; shutting down.
>
> To ...

You can't. If you could, I don't know what would happen.

On Sat, Aug 28, 2010 at 07:54, meganbkratz <email address hidden> wrote:

> Hmm, I didn't check cause I had a cell at the time. I'll check monday. What
> happens if you make the camera region larger than the 512 X 512ish region?
>
>