I was able to get stack trace in threads with kill -QUIT
Full thread dump:
"" tid=0x0x40207d40 this=0x0x26e10:
"" tid=0x0x41aa7bb0 this=0x0x114ed8:
at (wrapper managed-to-native) System.IO.MonoIO.GetFileStat
(string,System.IO.MonoIOStat&,System.IO.MonoIOError&) <0x00004>
at (wrapper managed-to-native) System.IO.MonoIO.GetFileStat
(string,System.IO.MonoIOStat&,System.IO.MonoIOError&) <0xffffff
at System.IO.File.GetCreationTime (string) <0x00036>
at System.IO.DefaultWatcher.DoFiles
(System.IO.DefaultWatcherData,string,bool) <0x009c9>
"" tid=0x0x41023bb0 this=0x0x26898:
at System.IO.DefaultWatcher.DoFiles
(System.IO.DefaultWatcherData,string,bool) <0x00167>
"" tid=0x0x40f22bb0 this=0x0x26c80:
at (wrapper managed-to-native) System.Threading.Thread.Sleep_internal
(int) <0x00004>
at (wrapper managed-to-native) System.Threading.Thread.Sleep_internal
(int) <0xffffffff>
at System.Threading.Thread.Sleep (int) <0x00016>
at Mono.WebServer.ApplicationServer.RunServer () <0x000ae>
at (wrapper delegate-invoke) System.MulticastDelegate.invoke_void ()
<0xffffffff>
at (wrapper runtime-invoke) System.Object.runtime_invoke_void
(object,intptr,intptr,intptr) <0xffffffff>
"" tid=0x0x415dbbb0 this=0x0x114e10:
at (wrapper managed-to-native)
System.Threading.WaitHandle.WaitOne_internal (intptr,int,bool) <0x00004>
at (wrapper managed-to-native)
System.Threading.WaitHandle.WaitOne_internal (intptr,int,bool) <0xffffffff>
at System.Threading.WaitHandle.WaitOne (int,bool) <0x00066>
at Runner.Start () <0x000e6>
at (wrapper delegate-invoke) System.MulticastDelegate.invoke_void ()
<0xffffffff>
at (wrapper runtime-invoke) System.Object.runtime_invoke_void
(object,intptr,intptr,intptr) <0xffffffff>
"" tid=0x0x41bf8bb0 this=0x0x114640:
at (wrapper managed-to-native) System.Threading.Thread.Sleep_internal
(int) <0x00004>
at (wrapper managed-to-native) System.Threading.Thread.Sleep_internal
(int) <0xffffffff>
at System.Threading.Thread.Sleep (int) <0x00016>
at Mono.Remoting.Channels.Unix.UnixConnectionPool.ConnectionCollector
() <0x00029>
at (wrapper delegate-invoke) System.MulticastDelegate.invoke_void ()
<0xffffffff>
at (wrapper runtime-invoke) System.Object.runtime_invoke_void
(object,intptr,intptr,intptr) <0xffffffff>
at System.IO.DefaultWatcher.DoFiles
(System.IO.DefaultWatcherData,string,bool) <0x00167>
at System.IO.DefaultWatcher.DoFiles
(System.IO.DefaultWatcherData,string,bool) <0x00167>
at System.IO.DefaultWatcher.DoFiles
(System.IO.DefaultWatcherData,string,bool) <0x00167>
at System.IO.DefaultWatcher.DoFiles
(System.IO.DefaultWatcherData,string,bool) <0x00167>
at System.IO.DefaultWatcher.UpdateDataAndDispatch
(System.IO.DefaultWatcherData,bool) <0x0012b>
at System.IO.DefaultWatcher.Monitor () <0x00150>
at (wrapper delegate-invoke) System.MulticastDelegate.invoke_void ()
<0xffffffff>
at (wrapper runtime-invoke) System.Object.runtime_invoke_void
(object,intptr,intptr,intptr) <0xffffffff>
Does that ring any bells?
Best regards,
Michał Ziemski
--- Begin Message ---
Hi!
I am now migrating my server from home-based FC4
to a VPS with suse 10.0
I have vanilla instalations of mono 1.2.4 on both systems
I have some apps run by mod-mono.
Everything works on both machines.
On suse however, the app mod-moono-server2 process keeps using a lot of
cpu after
compiling. The bigger app is being compiled, the more cpu used afterwards.
I have tried debugging with gdb, bu I am unable to call mono_pmip (I get
"Could not open /proc/[wrong_pid]/status") Wrong pid is different from
the actual pid
by a small number (1-5).
Any ideas how to trace where the problem lies?
Best regards,
Michał Ziemski
_______________________________________________
Mono-list maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list
--- End Message ---
_______________________________________________
Mono-list maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list
