Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

MemoryError during scan

#58 
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

Reported by Virgil Dupras · September 16th, 2009 @ 12:36 PM

State: fixed
Milestone: none
Assigned to: Virgil Dupras Virgil Dupras

Activity

  1. Virgil Dupras
    Virgil Dupras
    • 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.

    October 3rd, 2009 @ 04:56 PM

  2. Virgil Dupras
    Virgil Dupras
    • State changed from accepted to fixed

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

    October 3rd, 2009 @ 05:38 PM

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.