Ticket #445 (closed defect)

Opened 10 years ago

Last modified 10 years ago

Leaking in memory to 4GB

Reported by: HiMax Owned by:
Priority: critical Milestone: Eraser 6.0.11
Component: Core Version: 6.0.10.2620
Keywords: Cc:
Processor Architecture: x64 (64-bit) Blocked By:
Blocking: Operating System: Windows XP

Description

I had Eraser 6.0.10.2620 (current stable) that was leaking in memory running erase of 120GB SSD drive with pseudo-rundom 1 pass every 30 minutes over 12 hours. It grew to 4GB in ram. I had replicated it several times over past week. I upgraded to 6.0.10.2719 it still does that. It starts at 30-70MB, but then "VM size" grows to many GB

Win XP Pro x64

Blocking

IdSummaryMilestone
#445└ Leaking in memory to 4GBEraser 6.0.11

Blocked by

IdSummaryMilestone
#445└ Leaking in memory to 4GBEraser 6.0.11

Attachments

Untitled-7.png​ (20.6 KB) - added by HiMax 10 years ago.
Untitled-8.png​ (3.3 KB) - added by HiMax 10 years ago.
Task options
Untitled-6.png​ (8.1 KB) - added by HiMax 10 years ago.
Eraser.exe running data
Untitled-9.png​ (11.9 KB) - added by HiMax 10 years ago.
Eraser.exe Task Manager data
Untitled-10.png​ (13.9 KB) - added by HiMax 10 years ago.
Erase Schedule
Untitled-13.png​ (7.7 KB) - added by HiMax 10 years ago.
Task Manager after Erase.exe is closed

Change History

comment:1 Changed 10 years ago by HiMax

Session: Tuesday, June 26, 2012 11:31:04 AM
Tuesday, June 26, 2012 11:45:48 AM Error Insufficient system resources exist to complete the requested service.

comment:2 Changed 10 years ago by HiMax

it's erasing FAT32 empty space on empty dive

Changed 10 years ago by HiMax

comment:3 Changed 10 years ago by Joel

Do you happen to know how to make a memory dump of the process?

Changed 10 years ago by HiMax

Task options

Changed 10 years ago by HiMax

Eraser.exe running data

Changed 10 years ago by HiMax

Eraser.exe Task Manager data

Changed 10 years ago by HiMax

Erase Schedule

Changed 10 years ago by HiMax

Task Manager after Erase.exe is closed

comment:4 Changed 10 years ago by Joel

Have you tried disabling cluster tip erasure?

comment:5 Changed 10 years ago by Joel

And I should warn you now that doing unused space erasures on your SSD will definitely wear it out. SSDs have a limited number of program/erase cycles before it will refuse to accept new data.

comment:6 Changed 10 years ago by Joel

I've got r2728 which may fix this. Please try the 6.0 nightly later today and see if it fixes your problem.

comment:7 Changed 10 years ago by Joel

  • Status changed from new to pending

comment:8 Changed 10 years ago by Joel

  • Milestone set to Eraser 6.0.11

comment:9 Changed 10 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.