Second Life Forums Archive - 1.12 "No Execute" bug.

Farallon Greyskin

Cranky Seal

Join date: 22 Jan 2006

Posts: 491

08-09-2006 13:17

Today truying the latest version of 1.12 I got a "Windows has halted this program becuase of a No Execute (NX) problem.

Previous versions ran ok on this system, current released versions also run fine including 1.11.3 released today:

CPU: Not supported (3400 Mhz) (P4-960)
Memory: 2048 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation (Driver ver 91.2

Graphics Card: GeForce 7800 GT/PCI/SSE2
OpenGL Version: 2.0.1

Coult not file a bug report in game so putting it here...

Kyrah Abattoir

cruelty delight

Join date: 4 Jun 2004

Posts: 2,786

08-09-2006 15:35

right click on "my computer" properties advanced, somewhere there is the DEP protection, add Secondlife in the allowed list

_____________________

tired of XStreetSL? try those!
apez http://tinyurl.com/yfm9d5b
metalife http://tinyurl.com/yzm3yvw
metaverse exchange http://tinyurl.com/yzh7j4a
slapt http://tinyurl.com/yfqah9u

Farallon Greyskin

Cranky Seal

Join date: 22 Jan 2006

Posts: 491

08-15-2006 18:45

I did that and as I expected SL crashed to the desktop at that exact point. Seriously, executing data as code is just not going to work ;D

Kyrah Abattoir

cruelty delight

Join date: 4 Jun 2004

Posts: 2,786

08-15-2006 21:56

itsnot because it isn't a good coding habit that it doesn't work

_____________________

tired of XStreetSL? try those!
apez http://tinyurl.com/yfm9d5b
metalife http://tinyurl.com/yzm3yvw
metaverse exchange http://tinyurl.com/yzh7j4a
slapt http://tinyurl.com/yfqah9u

Farallon Greyskin

Cranky Seal

Join date: 22 Jan 2006

Posts: 491

08-16-2006 16:03

Er, yes, I happen to be a professional programmer for 20 years now. Also a software development team manager.

In this case, Windows caught the instruction pointer jumping into memory marked as data (It was a software detection not the hardware NX bit). It would be unlikely that executing data as code would NOT cause serious problems with the running of a program. It is a rather common bug and it always results in the halting of a program pretty fast (unless a virus writer is exploiting this bug in a program by loading executable code into data areas). At no time is any code that would cause that error a "good coding habit". (unless you are a virus writer)

The MOST LIKEY explaination IS a bad code, a stack corruption or trashed function pointer, and in this case it is almost 100% surely within the SL codebase. Possibly there is a path taken due to the specific driver version on my machine which is why I inlcuded the drvier version numbers.

Argent Stonecutter

Emergency Mustelid

Join date: 20 Sep 2005

Posts: 20,263

08-16-2006 16:12

From: Farallon Greyskin

From: someone

you are programmer now?

Er, yes, I happen to be a professional programmer for 20 years now.

Love that comeback.

Kelly Linden

Linden Developer

Join date: 29 Mar 2004

Posts: 896

08-16-2006 22:31

I am not tech support, and the following is not 'official' advice or support.

I have recently seen reports that nVidia 7xxx, particuarly 7800 varieties, and the 9X.xx series of drivers, are causing some pretty severe problems with Second Life. Or that Second Life is causing some problems with systems running that hardware/driver combination.

We have not successfully tracked down these issues. However, in some cases, rolling back the driver to the last official 8X.xx version has been more stable. This may not be desirable for your situation depending on the other software on your computer.

It is very odd that this particular version of Second Life causes this. I was not aware of any particuarly "interesting" changes in the latest preview release that would be likely to cause the indicated behavior. And no, we don't generally (or at all to my knowledge) try to execute code in the data areas.

If you could after the next crash, see if it actually manages to write any logs (on windows these are in C:\Documents and Settings\<user>\Application Data\SecondLife\logs), I would appreciate it if you could email them to me - [email]kelly@lindenlab.com[/email].

When exactly do you get this error? Is it before the login screen? While in world? If it is after the log in screen, have you tried logging into a different location? I ask these because it is possible that the client's handling of a specific piece or pieces of content in world could trigger the bug.

And lastly, just to cover bases, since it is a very virus like error - you have run a virus scan recently?

Also bug reports can be submitted directly to [email]bugs@lindenlab.com[/email]. The inworld bug report tool is actually a fancy front end to this email address, that also sends along some of the viewer logs.

_____________________

- Kelly Linden

Ron Overdrive

Registered User

Join date: 10 Jul 2005

Posts: 1,002

08-17-2006 18:55

From: Kelly Linden

I am not tech support, and the following is not 'official' advice or support.

I have recently seen reports that nVidia 7xxx, particuarly 7800 varieties, and the 9X.xx series of drivers, are causing some pretty severe problems with Second Life. Or that Second Life is causing some problems with systems running that hardware/driver combination.

We have not successfully tracked down these issues. However, in some cases, rolling back the driver to the last official 8X.xx version has been more stable. This may not be desirable for your situation depending on the other software on your computer.

It is very odd that this particular version of Second Life causes this. I was not aware of any particuarly "interesting" changes in the latest preview release that would be likely to cause the indicated behavior. And no, we don't generally (or at all to my knowledge) try to execute code in the data areas.

If you could after the next crash, see if it actually manages to write any logs (on windows these are in C:\Documents and Settings\<user>\Application Data\SecondLife\logs), I would appreciate it if you could email them to me - [email]kelly@lindenlab.com[/email].

When exactly do you get this error? Is it before the login screen? While in world? If it is after the log in screen, have you tried logging into a different location? I ask these because it is possible that the client's handling of a specific piece or pieces of content in world could trigger the bug.

And lastly, just to cover bases, since it is a very virus like error - you have run a virus scan recently?

Also bug reports can be submitted directly to [email]bugs@lindenlab.com[/email]. The inworld bug report tool is actually a fancy front end to this email address, that also sends along some of the viewer logs.

Some people Kelly cannot just roll back to the 8x.xx series. Prime example are those with the 7950GX2 based cards. Reason being is the 8x.xx series drivers are NOT coded to support dual GPU chipsets, the 91.xx drivers are. Telling them to downgrade to a driver that isn't coded for their card is like telling someone with a Skyline GT-R to use american regular 87 octain gas, it just ain't happening.

From my experiences, alot of the problems SL was having with the 91.xx drivers was on the client side not the drivers. When I first started using the 91.xx drivers when 1.10 came out my avitar would go all black with avitar vertex shader. Very much like how ATI cards had a similar problem with avitars going all green. LL's answer was roll back to 84.21, I stuck with my 91.xx drivers. When the client got fixed for the ATI guys my problem went away too. Performance from the 91.xx drivers were also extremely good in SL till 1.11 came out. The 91.xx drivers are currently rated by nVidia enthusiests to be the best nVidia drivers yet in terms of Image Quality and Performance, SL is the only "game" having issues with it.

1.12 "No Execute" bug.
Farallon Greyskin Cranky Seal Join date: 22 Jan 2006 Posts: 491	08-09-2006 13:17 Today truying the latest version of 1.12 I got a "Windows has halted this program becuase of a No Execute (NX) problem. Previous versions ran ok on this system, current released versions also run fine including 1.11.3 released today: CPU: Not supported (3400 Mhz) (P4-960) Memory: 2048 MB OS Version: Microsoft Windows XP Service Pack 2 (Build 2600) Graphics Card Vendor: NVIDIA Corporation (Driver ver 91.2 Graphics Card: GeForce 7800 GT/PCI/SSE2 OpenGL Version: 2.0.1 Coult not file a bug report in game so putting it here...
Kyrah Abattoir cruelty delight Join date: 4 Jun 2004 Posts: 2,786	08-09-2006 15:35 right click on "my computer" properties advanced, somewhere there is the DEP protection, add Secondlife in the allowed list _____________________ tired of XStreetSL? try those! apez http://tinyurl.com/yfm9d5b metalife http://tinyurl.com/yzm3yvw metaverse exchange http://tinyurl.com/yzh7j4a slapt http://tinyurl.com/yfqah9u
Farallon Greyskin Cranky Seal Join date: 22 Jan 2006 Posts: 491	08-15-2006 18:45 I did that and as I expected SL crashed to the desktop at that exact point. Seriously, executing data as code is just not going to work ;D
Kyrah Abattoir cruelty delight Join date: 4 Jun 2004 Posts: 2,786	08-15-2006 21:56 itsnot because it isn't a good coding habit that it doesn't work _____________________ tired of XStreetSL? try those! apez http://tinyurl.com/yfm9d5b metalife http://tinyurl.com/yzm3yvw metaverse exchange http://tinyurl.com/yzh7j4a slapt http://tinyurl.com/yfqah9u
Farallon Greyskin Cranky Seal Join date: 22 Jan 2006 Posts: 491	08-16-2006 16:03 Er, yes, I happen to be a professional programmer for 20 years now. Also a software development team manager. In this case, Windows caught the instruction pointer jumping into memory marked as data (It was a software detection not the hardware NX bit). It would be unlikely that executing data as code would NOT cause serious problems with the running of a program. It is a rather common bug and it always results in the halting of a program pretty fast (unless a virus writer is exploiting this bug in a program by loading executable code into data areas). At no time is any code that would cause that error a "good coding habit". (unless you are a virus writer) The MOST LIKEY explaination IS a bad code, a stack corruption or trashed function pointer, and in this case it is almost 100% surely within the SL codebase. Possibly there is a path taken due to the specific driver version on my machine which is why I inlcuded the drvier version numbers.
Argent Stonecutter Emergency Mustelid Join date: 20 Sep 2005 Posts: 20,263	08-16-2006 16:12 From: Farallon Greyskin From: someone you are programmer now? Er, yes, I happen to be a professional programmer for 20 years now. Love that comeback.
Kelly Linden Linden Developer Join date: 29 Mar 2004 Posts: 896	08-16-2006 22:31 I am not tech support, and the following is not 'official' advice or support. I have recently seen reports that nVidia 7xxx, particuarly 7800 varieties, and the 9X.xx series of drivers, are causing some pretty severe problems with Second Life. Or that Second Life is causing some problems with systems running that hardware/driver combination. We have not successfully tracked down these issues. However, in some cases, rolling back the driver to the last official 8X.xx version has been more stable. This may not be desirable for your situation depending on the other software on your computer. It is very odd that this particular version of Second Life causes this. I was not aware of any particuarly "interesting" changes in the latest preview release that would be likely to cause the indicated behavior. And no, we don't generally (or at all to my knowledge) try to execute code in the data areas. If you could after the next crash, see if it actually manages to write any logs (on windows these are in C:\Documents and Settings\<user>\Application Data\SecondLife\logs), I would appreciate it if you could email them to me - [email]kelly@lindenlab.com[/email]. When exactly do you get this error? Is it before the login screen? While in world? If it is after the log in screen, have you tried logging into a different location? I ask these because it is possible that the client's handling of a specific piece or pieces of content in world could trigger the bug. And lastly, just to cover bases, since it is a very virus like error - you have run a virus scan recently? Also bug reports can be submitted directly to [email]bugs@lindenlab.com[/email]. The inworld bug report tool is actually a fancy front end to this email address, that also sends along some of the viewer logs. _____________________ - Kelly Linden
Ron Overdrive Registered User Join date: 10 Jul 2005 Posts: 1,002	08-17-2006 18:55 From: Kelly Linden I am not tech support, and the following is not 'official' advice or support. I have recently seen reports that nVidia 7xxx, particuarly 7800 varieties, and the 9X.xx series of drivers, are causing some pretty severe problems with Second Life. Or that Second Life is causing some problems with systems running that hardware/driver combination. We have not successfully tracked down these issues. However, in some cases, rolling back the driver to the last official 8X.xx version has been more stable. This may not be desirable for your situation depending on the other software on your computer. It is very odd that this particular version of Second Life causes this. I was not aware of any particuarly "interesting" changes in the latest preview release that would be likely to cause the indicated behavior. And no, we don't generally (or at all to my knowledge) try to execute code in the data areas. If you could after the next crash, see if it actually manages to write any logs (on windows these are in C:\Documents and Settings\<user>\Application Data\SecondLife\logs), I would appreciate it if you could email them to me - [email]kelly@lindenlab.com[/email]. When exactly do you get this error? Is it before the login screen? While in world? If it is after the log in screen, have you tried logging into a different location? I ask these because it is possible that the client's handling of a specific piece or pieces of content in world could trigger the bug. And lastly, just to cover bases, since it is a very virus like error - you have run a virus scan recently? Also bug reports can be submitted directly to [email]bugs@lindenlab.com[/email]. The inworld bug report tool is actually a fancy front end to this email address, that also sends along some of the viewer logs. Some people Kelly cannot just roll back to the 8x.xx series. Prime example are those with the 7950GX2 based cards. Reason being is the 8x.xx series drivers are NOT coded to support dual GPU chipsets, the 91.xx drivers are. Telling them to downgrade to a driver that isn't coded for their card is like telling someone with a Skyline GT-R to use american regular 87 octain gas, it just ain't happening. From my experiences, alot of the problems SL was having with the 91.xx drivers was on the client side not the drivers. When I first started using the 91.xx drivers when 1.10 came out my avitar would go all black with avitar vertex shader. Very much like how ATI cards had a similar problem with avitars going all green. LL's answer was roll back to 84.21, I stuck with my 91.xx drivers. When the client got fixed for the ATI guys my problem went away too. Performance from the 91.xx drivers were also extremely good in SL till 1.11 came out. The 91.xx drivers are currently rated by nVidia enthusiests to be the best nVidia drivers yet in terms of Image Quality and Performance, SL is the only "game" having issues with it.

Welcome to the Second Life Forums Archive

1.12 "No Execute" bug.