Ticket #327 (closed defect: fixed)
error when highlighting multiple files, right clicking and choosing Erase
| Reported by: | selflove | Owned by: | Joel |
|---|---|---|---|
| Priority: | minor | Milestone: | Eraser 6.0.7 |
| Component: | User Interface (UX) | Version: | 6.0.6.1376 |
| Keywords: | Cc: | ||
| Processor Architecture: | i386 (32-bit) | Blocked By: | |
| Blocking: | Operating System: | Windows XP |
Description
- use Win XP Pro 32 bit and without Eraser loaded in RAM.
- highlight two installer EXE files. (I was trying to erase the two EXE insallers from http://www.microsoft.com/whdc/xps/viewxps.mspx)
- right click and choose to Erase them.
- You may get an error.
The first time the error occurred to me I was able to reproduce it twice more immediately after (while Eraser was loaded in RAM). But later, the file was actually able to be erased and I tried to reproduce it more but wasn't able to. Total reproduction rate is 3 out of 10.
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #327 | └ error when highlighting multiple files, right clicking and choosing Erase | Eraser 6.0.7 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #327 | └ error when highlighting multiple files, right clicking and choosing Erase | Eraser 6.0.7 |
Attachments
-
eraser error.png
(160.3 KB) -
added by selflove 2 years ago.
Change History
comment:1 Changed 2 years ago by selflove
I was able to reproduce the problem again and this time attached a screenshot.
I did not have Eraser loaded in RAM when I highlighted the files and chose to Erase them.
The error says "Eraser cannot connect to the running instance for erasures".
Note that in the screenshot that Eraser shows up in Task Manager after choosing to Erase, but the icon does not show up in the system tray.
comment:2 Changed 2 years ago by selflove
After Clicking OK on the error message, the Eraser.exe still shows up in Task Manager but the Eraser user interface or system tray icon still does not display. I continue to have problems Erasing those files until I end task Eraser.exe.
I had Eraser set to NOT "hide when minimized". By default it's checkmarked to hide when minimized. I'm not sure if that has anything to do with the bug.
