4.0.0.9 Bug - "Scanning - press ESC to cancel".

[chrisjj]

Windows 7.

Drag folder to filelist frequently gives "Scanning - press ESC to cancel" indefinitely - and ESC has no effect.

I did not see this on previous BRU versions.

Workaround: Instead use "Jump to path..."

[Admin]

Thanks, how to recreate this issue? What frequency causes this issue?

[chrisjj]

Thanks, how to recreate this issue?

Just darg in a folder.

And hope you don't get:



which is frequent on this operation newly on 4.0.0.9.

What frequency causes this issue?

Approx. 50%.

[Admin]

Is it caused by a specific folder ?
Do you have custom column defined in BRU, a JavaScript setup, or extracting exif or file properties?

[therube]

Drag folder to filelist frequently gives "Scanning - press ESC to cancel" indefinitely - and ESC has no effect.

I'm seeing that - in 4009, 4008, & 4007.
4006 works correctly.

Win7 x64, BRU x86.

Note that the file list window is "empty" - except for said message.
Statusbar correctly shows the number of items in said dragged directory.
The "urlbar" does correctly show the path of the said dragged directory.

The "items" are there in the file list window, yet you cannot see them.
You can F2 (rename) them, during which time they do appear, momentarily.




On my Win7, I have all "visual effects" (whatever MS calls that ... crap [can't think of name, ATM] disabled (so I basically look like XP [in case that matters]).



(I've not seen the actual crash that the OP is getting.
Though I've never dragged a directory like this before, either.)


> Is it caused by a specific folder ?

No.

> Do you have custom column defined in BRU, a JavaScript setup, or extracting exif or file properties?

No.

[chrisjj]

Thanks for the confirmation and excellent detail.

I do love BRU, but I am quite disappointed by the number of bugs introduced by updates. I'd take fewer updates, but then I'd not get the needed bug fixes.

[Admin]

Thank you for the great details, we are fixing this asap. Sorry for this issue
It only happens for folders dragged into BRU not files.

[chrisjj]

Thank you for the great details, we are fixing this asap.

Great! Thanks.

[chrisjj]

It only happens for folders dragged into BRU not files.

The "Stopped working" happens for files too.

1 On Windows 7 Launch BRU 4.0.0.9:



Note the engaged but empty Filters. I've seen this often before various crashes.

2 Drag in single EML file to the file list.

Result:

[chrisjj]

Workaround: Instead use "Jump to path..."

Quicker: in folder list, click a different folder, then click the original folder.

[Admin]

The folder drop and drag issue is fixed but not the file one... we can't recreate that one. IS it a file with very long path > 256?

[chrisjj]

The folder drop and drag issue is fixed

Thanks.

but not the file one... we can't recreate that one. IS it a file with very long path > 256?

I don't know. As the moment it is not happening, probably because BRU launch is not in the "engaged but empty Filters" state which I suspect is a prerequisite.

Do you know what causes this state? I suspect a BRU launch-time load of a .BRU file has failed. See the screenshot title bar has no .BRU mentioned.

[Admin]

Great info! I think we got it now: if a BRU file is loaded, and then BRU is closed and then reopened, but that same profile is no longer present, then BRU will go into all values blank. And then if you drag files into it, it crashes.
Note that if one manually sets all values to blank, it does not crash. Thanks, we are fixing this.

[chrisjj]

Great info! I think we got it now: if a BRU file is loaded, and then BRU is closed and then reopened, but that same profile is no longer present, then BRU will go into all values blank. And then if you drag files into it, it crashes.

That fits! "that same profile is no longer present" happens when I rename the folder containing portable BRU and the .BRU:

Note that if one manually sets all values to blank, it does not crash.

I guess there's a hidden invalid .BRU parameter.

Thanks, we are fixing this.

Great. Thanks. Could you please include alert on the .BRU load fail? Especially as it seems you're storing a full path to the BRU which is going to break if the portable installation USB stick drive letter changes.

And perhaps you'd consider fixing this portability fail?