[TLB 3.0] Explorer crashes

Well, I *was* having the problem and was prepearing a bug report, but initial testing of v2.2 is showing good signs. No crashes so far!

I get this error when right clicking on TLB 3.0:

Code:

Event Type:    Information
Event Source:    Application Popup
Event Category:    None
Event ID:    26
Date:        7/16/2004
Time:        11:21:37 AM
User:        N/A
Computer:    HAL-9000
Description:
Application popup: Explorer.EXE - Application Error : The instruction at "0x00c9415b" referenced memory at "0x00000000". The memory could not be "written".

The instruction address is always of the pattern 0x????415b

This did not happen with any other versions of TLB. Running WinXP SP2 Build 2162. Can also confirm that it is a problem with Build 2149 (RC2). You will probably need more information, just let me know what details you need and I will be more than happy to get that info to you.

PROBLEM SOLVED
DEP was the culprit. I hope that when final SP2 comes out that they disable that crap by default.

hi!

i also use TLB 3.0 on win xp sp1.
plugins: volume control, network mon, spacer

i also have explorer crashes from time to time. when they appear then always in the following situation:
i open my menu, that contains links to all drives, and right-click one of the drive-links.

what will happen: explorer will just disappear without an error message and a few seconds a later a new instance of explorer will automatically be launched.

regards,

rh

PROBLEM SOLVED
DEP was the culprit. I hope that when final SP2 comes out that they disable that crap by default.

Is DEP Data Execution Prevention???

Yes it is, and I can confirm that the problem still exists on SP2 RTM (Build 2180).

If you go into DEP conficuration it has option to exclude some selected software, Winamp cept constantly crashing with the mplayer plug-in until I added it to the exclusion list although I have no idea how this works.

If I understand correctly, DEP means that code will not be executed if it is in a data section of memory. This could prevent many buffer overflow security issues...

I must admit, I have no clue why there should be an ignore list, perhaps there is a reason why programs put code in data sections...? I wouldn't even know how to control this...

As I know DEP protect of executing code from data sections only. But in all cases program must crash. If DEP is turned on then program crash on DEP exception if DEP is turned off then crash because jump to invalid address. The problem is that TLB runs code from other DLL's when show context menu.

Ok, I was just talking about DEP in general, unrelated to the reported problem in TLB....

In your example, with DEP the program will crash, but without DEP it will crash if you're lucky, and it will execute the code if you're unlucky... that's the idea of a buffer overrun, isn't it?

Anyway, next week SP2 will be available to everyone (at least, that's what they tell us), so we can all go test TLB

Okay, found the true culprit with right click crashing explorer when DEP was activated... Something that I had done about 6 builds back when I was having trouble with new SP2 firewall service.

Sorry Yuri if you spent any time on this. ???