Unexpectedly Quit after 8 hours

[Only A Hobo]

I have been running LW 4.11.1 Pro for about 8 hours. Sharing 3000 files. It has just "unexpectedly quit" I have had 30 - 40 uploads ...mp3s and downloaded one mp3 and was I the process of downloading 2 more mp3s and they seem to have not completed. I was browsing at the time of the crash .. and was previously working with Photoshop, but closed that 1/2 hour ago.


Mac OSX 10.3.9 400MHZ Power PC G3 Blue and White 320MB Memory Free space on start up disk 4.11GB

Forgive me if the report should have been whittled down differently. I'm not quite sure what info is helpful .. I shall see if I can do a stack trace.????


This is the start apple Crash report excluding Threads 5-10 further "threads" did not indicate "crashed" but I've got the rest of the report if you want it.

----------------------------------------
Date/Time: 2006-05-26 19:18:34 +0100
OS Version: 10.3.9 (Build 7W98)
Report Version: 2

Command: LimeWire
Path: /Applications/LimeWire/LimeWire.app/Contents/MacOS/LimeWire
Version: 4.11.1 Pro (LimeWire 4.11.1 Pro)
PID: 482
Thread: 11

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000010

Thread 0:
0 com.apple.CoreFoundation 0x901c6a98 CFArrayAppendValue + 0x34
1 com.apple.CoreFoundation 0x901c1aac CFSetApplyFunction + 0xf8
2 com.apple.CoreFoundation 0x901c2710 __CFRunLoopDoObservers + 0xac
3 com.apple.CoreFoundation 0x901c237c __CFRunLoopRun + 0x474
4 com.apple.CoreFoundation 0x901c69e4 CFRunLoopRunSpecific + 0x148
5 com.apple.HIToolbox 0x92886e10 RunCurrentEventLoopInMode + 0xac
6 com.apple.HIToolbox 0x9288d53c ReceiveNextEventCommon + 0x17c
7 com.apple.HIToolbox 0x928af638 BlockUntilNextEventMatchingListInMode + 0x60
8 com.apple.AppKit 0x92e82258 _DPSNextEvent + 0x180
9 com.apple.AppKit 0x92e98cd8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 0x74
10 com.apple.AppKit 0x92ead058 -[NSApplication run] + 0x21c
11 libawt.jnilib 0x8108bc3c +[AWTStarter startAWT:] + 0xd0
12 com.apple.Foundation 0x90a4b0a0 __NSFireMainThreadPerform + 0x108
13 com.apple.CoreFoundation 0x902151b0 __CFRunLoopPerformPerform + 0x88
14 com.apple.CoreFoundation 0x901c4800 __CFRunLoopDoSources0 + 0x1fc
15 com.apple.CoreFoundation 0x901c20b8 __CFRunLoopRun + 0x1b0
16 com.apple.CoreFoundation 0x901c69e4 CFRunLoopRunSpecific + 0x148
17 ...ple.JavaApplicationLauncher 0x81f338b4 _Z11startupJavaiiPPKcPK14__CFDictionary14BuilderVe rsionS0_S1_ + 0x128
18 com.limegroup.gnutella 0x000043f0 0x1000 + 0x33f0
19 com.limegroup.gnutella 0x00004270 0x1000 + 0x3270

Thread 1:
0 libSystem.B.dylib 0x900078b8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007438 mach_msg + 0x38
2 libjvm.dylib 0x96f283b8 JVM_GetClassAccessFlags + 0x1168
3 libjvm.dylib 0x96f5b0f4 __divdi3 + 0x50f4
4 libjvm.dylib 0x9701e06c JVM_Halt + 0x251c
5 libjvm.dylib 0x9701e3d8 JVM_Halt + 0x2888
6 ...ple.JavaApplicationLauncher 0x81f33ac8 startJavaApplication + 0x1ac
7 ...ple.JavaApplicationLauncher 0x81f338e4 _Z14java_main_stubPv + 0x10
8 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 2 Crashed:
0 libSystem.B.dylib 0x900158f4 _fmt + 0x2d8
1 libSystem.B.dylib 0x9001d5f0 strftime + 0x50
2 libSystem.B.dylib 0x9002a0dc syslog + 0xfc
3 libjvm.dylib 0x970c5d8c JVM_UnloadLibrary + 0x8447c
4 libjvm.dylib 0x970c6108 JVM_UnloadLibrary + 0x847f8
5 libjvm.dylib 0x9702171c JVM_FreeMemory + 0x87c
6 libjvm.dylib 0x9700020c JNI_CreateJavaVM_Impl + 0x452c
7 libjvm.dylib 0x97000160 JNI_CreateJavaVM_Impl + 0x4480
8 libjvm.dylib 0x970f290c JVM_UnloadLibrary + 0xb0ffc
9 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 3:
0 libSystem.B.dylib 0x900078b8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007438 mach_msg + 0x38
2 libjvm.dylib 0x96f283b8 JVM_GetClassAccessFlags + 0x1168
3 libjvm.dylib 0x96f5b094 __divdi3 + 0x5094
4 libjvm.dylib 0x96f46868 JVM_GetMethodIxLocalsCount + 0x17d8
5 libjvm.dylib 0x96f70dfc JVM_GetMethodIxModifiers + 0x65c
6 libjvm.dylib 0x9701847c JVM_GetInterfaceVersion + 0x17a4c
7 libjvm.dylib 0x970f290c JVM_UnloadLibrary + 0xb0ffc
8 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 4:
0 libSystem.B.dylib 0x900078b8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007438 mach_msg + 0x38
2 libjvm.dylib 0x96f283b8 JVM_GetClassAccessFlags + 0x1168
3 libjvm.dylib 0x96f22d18 _mh_dylib_header + 0x2d18
4 libjvm.dylib 0x96f2c184 __cmpdi2 + 0x1ad4
5 libjvm.dylib 0x96f28898 JVM_MonitorWait + 0x108
6 <<00000000>> 0x04736580 0 + 0x4736580
7 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
8 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
9 <<00000000>> 0x0472d16c 0 + 0x472d16c
10 libjvm.dylib 0x96f3afe8 JVM_GetCPMethodClassNameUTF + 0xb38
11 libjvm.dylib 0x96f5c438 JVM_GetCPClassNameUTF + 0x998
12 libjvm.dylib 0x96f99098 JVM_Close + 0x4b8
13 libjvm.dylib 0x96fa9960 JVM_Interrupt + 0x2e0
14 libjvm.dylib 0x9704e6fc JVM_UnloadLibrary + 0xcdec
15 libjvm.dylib 0x96f94df4 JVM_FindClassFromClass + 0xc14
16 libjvm.dylib 0x970f290c JVM_UnloadLibrary + 0xb0ffc
17 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 11 Crashed:
0 libSystem.B.dylib 0x900158f4 _fmt + 0x2d8
1 libSystem.B.dylib 0x9001d5f0 strftime + 0x50
2 libSystem.B.dylib 0x9002a0dc syslog + 0xfc
3 libobjc.A.dylib 0x9083bcf0 _objc_syslog + 0xa4
4 libobjc.A.dylib 0x9083bdb4 _objc_error + 0x4c
5 libobjc.A.dylib 0x9083bd44 __objc_error + 0x40
6 libobjc.A.dylib 0x90831b50 _internal_class_createInstanceFromZone + 0x70
7 com.apple.Foundation 0x90a22314 NSAllocateObject + 0x60
8 com.apple.AppKit 0x92fcb3a0 +[NSColor colorWithDeviceRed:green:blue:alpha:] + 0x40
9 com.apple.AppKit 0x92fbd788 -[NSCalibratedRGBColor colorUsingColorSpaceName:device:] + 0x11c
10 com.apple.AppKit 0x92edfde8 -[NSCatalogColor colorUsingColorSpaceName:device:] + 0x188
11 libawt.jnilib 0x81077dd0 Java_apple_awt_CColorPaint_getNativeRGB + 0x70
12 <<00000000>> 0x04a9e360 0 + 0x4a9e360
13 <<00000000>> 0x04a9e168 0 + 0x4a9e168
14 <<00000000>> 0x04d80ee4 0 + 0x4d80ee4
15 <<00000000>> 0x04d81644 0 + 0x4d81644
16 <<00000000>> 0x04d7f4dc 0 + 0x4d7f4dc
17 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
18 <<00000000>> 0x04ddf198 0 + 0x4ddf198
19 <<00000000>> 0x049bf618 0 + 0x49bf618
20 <<00000000>> 0x04993f70 0 + 0x4993f70
21 <<00000000>> 0x0497bf94 0 + 0x497bf94
22 <<00000000>> 0x049217f0 0 + 0x49217f0
23 <<00000000>> 0x0497c034 0 + 0x497c034
24 <<00000000>> 0x04a36168 0 + 0x4a36168
25 <<00000000>> 0x04b03274 0 + 0x4b03274
26 <<00000000>> 0x049fdbdc 0 + 0x49fdbdc
27 <<00000000>> 0x04afdc04 0 + 0x4afdc04
28 <<00000000>> 0x0485cadc 0 + 0x485cadc
29 <<00000000>> 0x049e7220 0 + 0x49e7220
30 <<00000000>> 0x0485a3a4 0 + 0x485a3a4
31 <<00000000>> 0x04afcaf0 0 + 0x4afcaf0
32 <<00000000>> 0x047a4680 0 + 0x47a4680
33 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
34 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
35 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
36 <<00000000>> 0x0472d16c 0 + 0x472d16c
37 libjvm.dylib 0x96f3afe8 JVM_GetCPMethodClassNameUTF + 0xb38
38 libjvm.dylib 0x96f5c438 JVM_GetCPClassNameUTF + 0x998
39 libjvm.dylib 0x96f99098 JVM_Close + 0x4b8
40 libjvm.dylib 0x96fa9960 JVM_Interrupt + 0x2e0
41 libjvm.dylib 0x9704e6fc JVM_UnloadLibrary + 0xcdec
42 libjvm.dylib 0x96f94df4 JVM_FindClassFromClass + 0xc14
43 libjvm.dylib 0x970f290c JVM_UnloadLibrary + 0xb0ffc
44 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

[Sam]

Ever have this happen before, Hobo? It doesn't look like it's triggered from anything new. And it certainly is an Apple bug if it's crashing the program. Probably a bug with the newer java release on OSX.

[Only A Hobo]

Sam .. I had problems with previous versions of LW 4.10 and settled on JUM 4.10.0. which works excellently for me. The problems were with disconnecting ..not crashing, I can't recall a previous LW crash off hand.

This is the first time I've run 4.11.1 I neglected to mention my Java version 1.4.2_09 btw.

I'll give it another run and see how this goes .. could have been me doing too much other stuff on the comp.

another thing I have noticed is that the window has not open up maximised but hopefully that was because of the crash.

I'll keep you posted :)

[Only A Hobo]

I have had no further problems, but have yet to put it to anything strenuous. My system is fairly aged and Opera, Adobe Photoshop and this once Limewire have occasionally crashed. I blame the comp ... It's time it was replaced :)

[Only A Hobo]

A further crash has occurred and I'm no expert but have a very wild theory. These crashes happened after or while running Dreamweaver or Photoshop simultaneously and the Memory (ram) use was stretched to the max. I know MacOSX will use Virtual memory to, as it were, take up the slack. Is it possible that LW is for some reason not actually using Virtual Memory for some reason. The VM on the Monitor runs sat about 2-3 GB when LW is running. Perhaps I just need more RAM (or a G5 lol)

In my previous post it says that thread 11 crashed .. can you explain to me just what that means please

[Only A Hobo]

I'm afraid to say the crashing has continued in the same pattern. I have reverted to 4.10.0JUM and will let you know how that goes for me .. Have a good day :)

[Only A Hobo]

As yet my 4.10.0 is using no more than 550MB virtual Memory, so it does look as if the Beta was using an awful lot more than this ..over 3GB on occasions, which seems to possibly be the cause of my problems with it.

[Only A Hobo]

:):) 4.11.2 is running well after 9 hours ... VM stable at 500 or so 28 threads ...No downloads prformed yet.:):)

[Only A Hobo]

Sorry to have to tell you this but 4.11.2 is giving me the same problem.

All was running well. I had an "uncaught thread error". sent the error report of and all continued fine, but then I started to download a single file, and the VM shot up from 680 to 1880 within an hour becoming Very sluggish shortly after this Limewire crashed, at what was probably about 2000 VM which seems to be the level at which a crash will happen.

Also the VM started to climb as the thread count went over 30 I saw it at 34 at the last look.

I've restarted it ... 28 threads .. 4 concurrent uploads and downloads awaitig busy hosts .

[Sam]

Do you recall what the error was that you saw before things went to hell? It (and other errors) should be listed in the OS X Console.

[Only A Hobo]

The error message said .."Uncaught thread error". not sure where I find the details ,, and the error message is not copiable, but I thought the message was sent to LW

PS I just closed LW down again ..ran for an hour or so ..one download and was up to 1.6GBB VM

from the OSX console Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000010
-------------------33 Threads recorded

Thread 2 Crashed:
0 libSystem.B.dylib 0x900158f4 _fmt + 0x2d8
1 libSystem.B.dylib 0x9001d5f0 strftime + 0x50
2 libSystem.B.dylib 0x9002a0dc syslog + 0xfc
3 libjvm.dylib 0x970c5d8c JVM_UnloadLibrary + 0x8447c
4 libjvm.dylib 0x970c6108 JVM_UnloadLibrary + 0x847f8
5 libjvm.dylib 0x9702171c JVM_FreeMemory + 0x87c
6 libjvm.dylib 0x9700020c JNI_CreateJavaVM_Impl + 0x452c
7 libjvm.dylib 0x97000160 JNI_CreateJavaVM_Impl + 0x4480
8 libjvm.dylib 0x970f290c JVM_UnloadLibrary + 0xb0ffc
9 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

------------------------------------------

Thread 11 Crashed:
0 libSystem.B.dylib 0x900158f4 _fmt + 0x2d8
1 libSystem.B.dylib 0x9001d5f0 strftime + 0x50
2 libSystem.B.dylib 0x9002a0dc syslog + 0xfc
3 libobjc.A.dylib 0x9083bcf0 _objc_syslog + 0xa4
4 libobjc.A.dylib 0x9083bdb4 _objc_error + 0x4c
5 libobjc.A.dylib 0x9083bd44 __objc_error + 0x40
6 libobjc.A.dylib 0x90831b50 _internal_class_createInstanceFromZone + 0x70
7 com.apple.Foundation 0x90a22314 NSAllocateObject + 0x60
8 com.apple.AppKit 0x92fcb3a0 +[NSColor colorWithDeviceRed:green:blue:alpha:] + 0x40
9 com.apple.AppKit 0x92fbd788 -[NSCalibratedRGBColor colorUsingColorSpaceName:device:] + 0x11c
10 com.apple.AppKit 0x92edfde8 -[NSCatalogColor colorUsingColorSpaceName:device:] + 0x188
11 libawt.jnilib 0x81077dd0 Java_apple_awt_CColorPaint_getNativeRGB + 0x70
12 <<00000000>> 0x048c42a0 0 + 0x48c42a0
13 <<00000000>> 0x048c40a8 0 + 0x48c40a8
14 <<00000000>> 0x04d677e4 0 + 0x4d677e4
15 <<00000000>> 0x04d67f44 0 + 0x4d67f44
16 <<00000000>> 0x04d7379c 0 + 0x4d7379c
17 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
18 <<00000000>> 0x04e4567c 0 + 0x4e4567c
19 <<00000000>> 0x0492aa18 0 + 0x492aa18
20 <<00000000>> 0x04891f70 0 + 0x4891f70
21 <<00000000>> 0x04945294 0 + 0x4945294
22 <<00000000>> 0x0492bcf0 0 + 0x492bcf0
23 <<00000000>> 0x04945334 0 + 0x4945334
24 <<00000000>> 0x04abfa68 0 + 0x4abfa68
25 <<00000000>> 0x0492f434 0 + 0x492f434
26 <<00000000>> 0x0489871c 0 + 0x489871c
27 <<00000000>> 0x048a9084 0 + 0x48a9084
28 <<00000000>> 0x0484061c 0 + 0x484061c
29 <<00000000>> 0x049a51a0 0 + 0x49a51a0
30 <<00000000>> 0x04858a64 0 + 0x4858a64
31 <<00000000>> 0x04be3cf0 0 + 0x4be3cf0
32 <<00000000>> 0x047a4680 0 + 0x47a4680
33 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
34 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
35 <<00000000>> 0x0472ffb0 0 + 0x472ffb0
36 <<00000000>> 0x0472d16c 0 + 0x472d16c
37 libjvm.dylib 0x96f3afe8 JVM_GetCPMethodClassNameUTF + 0xb38
38 libjvm.dylib 0x96f5c438 JVM_GetCPClassNameUTF + 0x998
39 libjvm.dylib 0x96f99098 JVM_Close + 0x4b8
40 libjvm.dylib 0x96fa9960 JVM_Interrupt + 0x2e0
41 libjvm.dylib 0x9704e6fc JVM_UnloadLibrary + 0xcdec
42 libjvm.dylib 0x96f94df4 JVM_FindClassFromClass + 0xc14
43 libjvm.dylib 0x970f290c JVM_UnloadLibrary + 0xb0ffc
44 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

[Lord of the Rings]

L 4.11.2 is already here & many bugs fixed. See how it handles on Panther with Java 1.4.2

[Only A Hobo]

Hi lotr ..This is page 2 of the threaad.. I'm now running 4.11.2 and getting the same problem. It seems to only happen when I start to download.

[stief]

Hi Hobo

Tried to check for your situation, using a different setup.

I ran 4.11.2 Pro on my G4 iBook (Tiger and Java 1.5) for 61 hrs as an UP, and the VMem got up to 1.35 GB. This is a slower rise than I saw with pre-4.10 releases, but still a rise.

CPU was high (usually above 40%), but no crashes. The G4 did get sluggish, but was bearable, for a beta.

Used up about 4 GB up and down in bandwidth (2GB each way), so file transfers don't trigger the VM rise with the newer java.

[Only A Hobo]

I just tried something. I dissabled iTunes integration and sharing, but this has not helped. However after 14 hours The VM was rising ... to 1.7GB when I dissconnected LW and no activity is occurring. (I disconnected as I want some d/l info off it before it crashes!) After a few brief D'ls when I opened LW VM was around 600 for the day in the last hour I have made several downloads and the VM rose during this time.
btw I have been running as a leaf only. cpu up to 50%

Stief ...no way could I run this for 61 hours ... so somewhere in my set up ..G3 Panther Leaf I'm afraid something is not agreeing with my comp. It does seem downloads are triggering the VM to rise, and rapidly, for me. and my downloads have not been large ones... a handful of mp3 song files only

[stief]

Hobo, when jum, sam and I were trying to figure out the VMem problem, I was using a G3 laptop. IIRC, hiding LW when not in use often helped minimize/workaround the problem.

Want me to see if the threads are still present in the archived beta forum for the tricks we tried?

[Only A Hobo]

Thanks Stief. It's not necessary as far as I'm concerned. I was just hoping to help out with the testing of the new Beta. I have Jum's 4.10.0 which works like a dream, and i shall put that back in if I can't get a Beta to work for me. I had problems with 4.10.5 or so Frostwire ... disconnecting, and that is when I discovered Jums fine work. .... I got this desire to get myself a G5 iMac .. until then .......... I have a LW which works for me on my antique computer lol.

[Sam]

I wonder what Jens does to make it work better.

[jum]

I wonder what Jens does to make it work better.

Well, as the build procedure is not open source the packaging might be different. Otherwise I have a few changes in my version, but I would not believe that these are related to this problem. I would recommend to check if one of my newer builds still work better, if yes it might be my changes. Otherwise it is simply the cvs state of the day the build was done that works better.