Opened 13 years ago
Closed 12 years ago
#161 closed defect (fixed)
Jeti/2 crashes on startup
Reported by: | Yoda_Java6 | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | GA4 |
Component: | general | Version: | 1.6.0 Build 25 GA3 |
Severity: | medium | Keywords: | |
Cc: |
Description (last modified by )
Jeti/2 still crashes on startup. Problem started with the GCC builds of Odin.
I have now tested every F*****
setting of Jeti/2 to see if any of those can be the difference between our tests.
Well, at the buttom (of course), the setting 'XMPP' seems to be the one causing the problem. When I turn it off, Jeti/2 can start again.
This setting have always been on here - and gives no problems with
Java 1.41, Java 1.42 or Java 1.5 - and also worked with VAC builds of ODIN.
Attachments (2)
Change History (46)
by , 13 years ago
Attachment: | Crash192.zip added |
---|
comment:1 by , 13 years ago
Description: | modified (diff) |
---|---|
Severity: | high → medium |
comment:2 by , 13 years ago
Milestone: | Enhanced → GA3 |
---|
follow-up: 5 comment:3 by , 12 years ago
follow-up: 6 comment:4 by , 12 years ago
Checked the code. Visually I don't see any problems. Can you quickly try the debug version? ftp://ftp.netlabs.org/pub/odin/test/od.zip. I need the odin*.log files of your failed attempts (and crash logs if any).
comment:5 by , 12 years ago
Replying to dmik:
I've checked it. Jeti/2 still fully works here with the latest b25 build.
Did you enable 'XMPP' as described above ? It only crashes here, when that is enabled.
However, your latest log shows that for you it crashes in IPHLPAPI.DLL (GetAdaptersInfo). Which suggests that you have some unusual network adapter configuration. I will check the code.
It crashes both on my laptops and my desktop PC. None of these uses the same drivers.
OpenFire also crashes in IPHLPAPI.DLL - again a completely different NIC setup.
comment:6 by , 12 years ago
Replying to dmik:
Checked the code. Visually I don't see any problems. Can you quickly try the debug version? ftp://ftp.netlabs.org/pub/odin/test/od.zip. I need the odin*.log files of your failed attempts (and crash logs if any).
All logs incl pdump available here:
comment:8 by , 12 years ago
I can confirm some strange behavior. It doesn't crash here but it gives 100% CPU load if I enable the XMPP plugin. This only happens with the release version of JDK. The debug version works well.
For some reason, the Win32 exception handler is not called in the release build (in the debug build it is). As a result, the unsatisfied exception gets raised again and again.
comment:10 by , 12 years ago
I found the reason why the exception handler did not work -- it's a small but nasty regression of http://svn.netlabs.org/odin32/changeset/21999. We didn't pick up the CONTEXT record changes made by the __except filter (if any). I fixed it now and it goes further but then it crashes at some debug assertion. I can't catch it though yet since the debugger is very unstable...
comment:11 by , 12 years ago
The Odin regression is fixed in r 22004 there.
The debug assertion is fixed in r391.
Now I get a valid crash report from JVM that shows that JVM tries to execute code on the stack (!) and then unsurprisingly crashes due to the access violation exception. This is weird. Looks like some memory gets corrupted.
comment:12 by , 12 years ago
Btw, can we get the source code of the Jeti/2 and especially of the XMPP plugin? Who has the contact of the author?
comment:14 by , 12 years ago
Just tested it once more with hotspot rebuilt with ODIN_FORCE_WIN32_TIB and it works... really strange.
comment:15 by , 12 years ago
Yoda, please check the debug hotspot build you may take here ftp://ftp.netlabs.org/pub/odin/test/od.zip with Jeti.
comment:16 by , 12 years ago
I downloaded that 7 days ago - and reported back.
It doesn't seem to be updated, so the reports are still the same ???
comment:17 by , 12 years ago
Mmm, the correct link is ftp://ftp.netlabs.org/pub/odin/test/hd.zip. My fault. Please try ASAP.
comment:19 by , 12 years ago
Sorry, I installed the DLL in the wrong place before.
After correcting it, I get a different crash:
ftp://ftp.warpspeed.dk/pdumps/LapCrash192.zip
Maybe this DLL doesn't work correctly with my GA2 version ?
comment:21 by , 12 years ago
Okay, my last guess that the new crash is because we:
- Don't maintain the win32 exception chain in non-ODIN_FORCE_WIN32_TIB mode
- Don't make sure that FS contains the right value around the place where hotspot detects the Thread pointer location (which it detects based on the contents of FS:[0] i.e. the pointer to the exception chain, see source:/trunk/openjdk/hotspot/src/os_cpu/windows_x86/vm/os_windows_x86.cpp).
1 is easy, 2 requires some thinking. This access logic of the Thread pointer is also used in the code that generates x86 assembly on the fly and I can't find MacroAssembler primitives that could load a desired value to FS so far...
comment:22 by , 12 years ago
Yoda, one more test please: ftp://ftp.netlabs.org/pub/odin/test/od2.zip and ftp://ftp.netlabs.org/pub/odin/test/hd2.zip.
comment:23 by , 12 years ago
Testing on my Desktop PC.
Jeti never initializes - something seems to be looping 4ever.
I stopped it with ctrl-C
Crash207.zip attached to this ticket
by , 12 years ago
Attachment: | Crash207.zip added |
---|
comment:24 by , 12 years ago
Tested with OpenFire too. It gives the same endless stack dumps in Odin log.
comment:25 by , 12 years ago
Hmm, looks like you also need the new JAVA.EXE version to properly test it. All the tests above are not valid w/o it. I've added JAVA.EXE as ftp://ftp.netlabs.org/pub/odin/test/jd2.zip. Please try again with it and JVM.DLL from hd2.zip.
Please also try another test with JVM.DLL from ftp://ftp.netlabs.org/pub/odin/test/hd3.zip and JAVA.EXE from ftp://ftp.netlabs.org/pub/odin/test/jd3.zip.
comment:26 by , 12 years ago
Added J2 (hd2 I already had).
Crash is now back to the usual one in IPHLPAPI.
Crash209.zip attached.
comment:27 by , 12 years ago
OK, too big to attach - it is here instead:
ftp://ftp.warpspeed.dk/pdumps/Crash209.zip
comment:28 by , 12 years ago
jd3 + hd3 added (Notice: hd3 is older than hd2 !).
Same crash in IPHLPAPI - another in POPUPLOG.OS2
ftp://ftp.warpspeed.dk/pdumps/Crash210.zip
If you need PDUMPS, I can enable them.
comment:29 by , 12 years ago
Ok, thx, I will analyze them and give you the new versions to test.
It looks like in your case it simply doesn't run to a point where it starts executing the stack here (hd2) since it crashes in IPHLPAPI.DLL. Doesn't explain anything to me so far...
comment:30 by , 12 years ago
Tested j2 on OpenFire.
Crashes seems different - 498 gave guard page errors again - 499 ran a bit further.
ftp://ftp.warpspeed.dk/pdumps/Crash498.zip
ftp://ftp.warpspeed.dk/pdumps/Crash499.zip
These include PDUMPS
comment:31 by , 12 years ago
Crash500.zip is OpenFire with j3 and hd3. Guard page warning again.
ftp://ftp.warpspeed.dk/pdumps/Crash500.zip
comment:32 by , 12 years ago
Found the bug. Should be fixed in Odin in r22006:
iphlpapi: Fix possible crash in GetAdaptersInfo?() and friends. This could happen under some circumstances due to invalid casting from int to char. Regression of the switch to GCC (which performs conversions differently compared to VAC).
The code was wrong and relied on non-standard VAC behavior.
Here's the fixed (debug) version of IPHLPAPI.DLL for you to test: ftp://ftp.netlabs.org/pub/odin//test/iphlpapid.zip. Check and report back please. Test JD2/HD2 first.
comment:33 by , 12 years ago
Note that JD3/HD3 is the build with the old SEH scheme (ODIN_FORCE_WIN32_TIB) and hence the old guard page warnings (and possible crashes) are back -- switching to the new scheme was done in particular to fix these guard page warnings and related problems.
comment:34 by , 12 years ago
Well, it doesn't seem to crash on startup now with JD2/HD2. It used to crash even
if server was unavailable (which it still is).
OpenFire still doesn't work with any of these builds - crashes at startup:
ftp://ftp.warpspeed.dk/pdumps/Crash503.zip
comment:35 by , 12 years ago
comment:36 by , 12 years ago
Well, I found an old account on another server to test.
I don't see any crashes in IPIHLPAPI any more - but it seems
to crash in several different ways now.
ftp://ftp.warpspeed.dk/pdumps/LapCrash204.zip
ftp://ftp.warpspeed.dk/pdumps/LapCrash205.zip
ftp://ftp.warpspeed.dk/pdumps/LapCrash206.zip
ftp://ftp.warpspeed.dk/pdumps/LapCrash207.zip
ftp://ftp.warpspeed.dk/pdumps/LapCrash208.zip
comment:37 by , 12 years ago
And how does it behave with JD3/HD3?
And when do the above crashes happen? Enabling XMPP plugin again?
comment:38 by , 12 years ago
It crashes when all is up, just before it is ready to use.
It doesn't matter if XMPP plugin is enabled or disabled.
Now, trying JD3/HD3 crash is gone, and Jeti/2 seems to work !
comment:39 by , 12 years ago
Milestone: | GA3 → GA4 |
---|---|
Version: | 1.6.0-b24 GA2 → 1.6.0 Build 25 GA3 |
These problems need to be analyzed further. Moving it to GA4.
comment:40 by , 12 years ago
Priority: | major → blocker |
---|
comment:41 by , 12 years ago
Seems that there is one more victim of the new SEH scheme - AOO. Java works in AOO (Apache OpenOffice) if I use GA2 (old SEH scheme) and hangs (with a crash in ODINCDT.DLL) if I use GA3. Here's the POPUPLOG:
07-27-2012 14:41:30 SYS3170 PID 00e9 TID 0001 Slot 00c1 D:\APPS\OPENOFFICE.ORG.3\PROGRAM\SOFFICE.BIN c0010002 118d00e2 P1=00000000 P2=XXXXXXXX P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=168d6514 ECX=00000000 EDX=de4a9dc7 ESI=168d6514 EDI=168d6440 DS=0053 DSACC=d0f3 DSLIM=5fffffff ES=0053 ESACC=d0f3 ESLIM=5fffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005b:1c3d07c9 CSACC=d0df CSLIM=5fffffff SS:ESP=0053:0012fe80 SSACC=d0f3 SSLIM=5fffffff EBP=0012fe98 FLG=00010213 ODINCRT.DLL 0002:000000e2
Created #179 for it.
comment:42 by , 12 years ago
The problem has been fixed in Odin, see r22009 there.
A really tiny bug, regression of switching to the new SEH scheme.
Jeti/2 doesn't crash here anymore when I turn on and off the XMPP plugin.
The test version of JDK.DLL is here: ftp://ftp.netlabs.org/pub/odin/test/j4.zip. Please test and report.
comment:43 by , 12 years ago
Tested j4 - and it does indeed seem like Jeti/2 is finally stable now :-)
I've checked it. Jeti/2 still fully works here with the latest b25 build. However, your latest log shows that for you it crashes in IPHLPAPI.DLL (GetAdaptersInfo). Which suggests that you have some unusual network adapter configuration. I will check the code.