Yet another bug in 1.7.0_21

[Roedy Green]

I got EXCEPTION_ACCESS_VIOLATION (0xc0000005) at
pc=0x000000006c883b08, pid=2360, tid=3932


in a large program I have been running for years without incident.

This the worst release I have ever seen. I started with Java =1,0

 

[Roedy Green]

I got EXCEPTION_ACCESS_VIOLATION (0xc0000005) at
pc=0x000000006c883b08, pid=2360, tid=3932

When run the same jar using jet runtime, it works fine.

 

[Lew]

Roedy Green wrote, quoted or indirectly quoted someone who said :

I got EXCEPTION_ACCESS_VIOLATION (0xc0000005) at
pc=0x000000006c883b08, pid=2360, tid=3932

When run the same jar [sic] using jet [sic] runtime, it works fine.

Long on the complaint, short on the details.

http://sscce.org/

 

[Arne Vajhøj]

I got EXCEPTION_ACCESS_VIOLATION (0xc0000005) at
pc=0x000000006c883b08, pid=2360, tid=3932

in a large program I have been running for years without incident.

In my experience then that type of error typical comes from
AWT not liking the graphics card.

Arne

 

[Roedy Green]

Long on the complaint, short on the details.

It had to happen in a huge program (this zip is 18 MB excluding of
sample data files) and refused to give any details about where in my
code the trouble was. At that point I just said, "This is a such a
mess. Others will be having trouble too. I have to back off to the
previous version".

I will wait until 1.7.0_23 is released and give it another try.

I really should do an SSCCE on the exec bug though. The string came
from a parser, not direct as I showed. It could be the parser doing
something strange under 1.7.0_21. I have some reason to think that is
not so, but should eliminate the possibility completely.