#58 ✓fixed
Virgil Dupras

MemoryError during scan

Reported by Virgil Dupras | 2009-09-16 12:36:57 UTC

Traceback (most recent call last):
  File "C:\src\dupeguru\pe\build\pyi.win32\dgpe\outPYZ1.pyz/hsutil.job", line 200, in _async_run
  File "C:\src\dupeguru\pe\build\pyi.win32\dgpe\outPYZ1.pyz/dupeguru.app", line 209, in do
  File "C:\src\dupeguru\pe\build\pyi.win32\dgpe\outPYZ1.pyz/dupeguru.scanner", line 86, in GetDupeGroups
  File "C:\src\dupeguru\pe\build\pyi.win32\dgpe\outPYZ1.pyz/dupeguru_pe.matchbase", line 44, in getmatches
  File "C:\src\dupeguru\pe\build\pyi.win32\dgpe\outPYZ1.pyz/dupeguru_pe.matchbase", line 114, in _do_getmatches
MemoryError

Comments and changes to this ticket

  • Virgil Dupras

    Virgil Dupras 2009-10-03 16:56:08 UTC

    • State changed from “new” to “accepted”
    • Assigned user set to “Virgil Dupras”

    After another analysis of the comparing code, it seems that the memory error likely happens because async_results holds a lots of very large lists.

    To avoid this, the async results should be "fetched" (result.get()) during the async_results population. so that these results can be popped out of the list right away.

  • Virgil Dupras

    Virgil Dupras 2009-10-03 17:38:02 UTC

    • State changed from “accepted” to “fixed”

    (from [174]) [#58 state:fixed] Moved the async results collection into the same loops as the async filler phase to avoid getting memory errors.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Shared Ticket Bins

People watching this ticket

Tags

Referenced by

Pages