Open GoogleCodeExporter opened 9 years ago
Interesting, I have never seen this issue...
I have slightly modified the code and compiled it in Debug. If it still crashes,
there will be line numbers in the log file which will be helpful. And if it
stops
crashing, there should be logs indicating what was wrong.
Please try this version and let me know:
http://hudson-tray-tracker.googlecode.com/files/HudsonTrayTrackerInstaller_v0.9.
6_beta.exe
Thanks.
Original comment by Alexis.S...@gmail.com
on 20 Nov 2009 at 2:56
Sure, i will get back to you next week!
Thanks alot
Original comment by par.toma...@gmail.com
on 20 Nov 2009 at 3:35
Hi Alexis!
I managed to get it crash again.
Here goes the log. I guess you will be able to figure it out now since the
error
message is alot better.
Thanks in advance, Tomas
2009-11-24 10:47:35,750 [STP SmartThreadPool Thread #0] INFO
Hudson.TrayTracker.BusinessComponents.HudsonService - Done updating project
2009-11-24 10:47:35,796 [6] INFO
Hudson.TrayTracker.BusinessComponents.ProjectsUpdateService - Done
2009-11-24 10:47:41,234 [1] ERROR
Hudson.TrayTracker.Utils.ThreadExceptionHandler -
Win32Exception - Error creating window handle.
2009-11-24 10:47:41,328 [1] ERROR
Hudson.TrayTracker.Utils.ThreadExceptionHandler -
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Timer.TimerNativeWindow.EnsureHandle()
at System.Windows.Forms.Timer.TimerNativeWindow.StartTimer(Int32 interval)
at System.Windows.Forms.Timer.set_Enabled(Boolean value)
at System.Windows.Forms.ToolStripManager.ModalMenuFilter.ProcessMessages(Boolean
process)
at System.Windows.Forms.ToolStripManager.ModalMenuFilter.EnterMenuModeCore()
at System.Windows.Forms.ToolStripManager.ModalMenuFilter.SetActiveToolStripCore
(ToolStrip toolStrip)
at System.Windows.Forms.ToolStripDropDown.ReparentToActiveToolStripWindow()
at System.Windows.Forms.ToolStripDropDown.SetVisibleCore(Boolean visible)
at System.Windows.Forms.ContextMenuStrip.SetVisibleCore(Boolean visible)
at System.Windows.Forms.ToolStripDropDown.Show(Int32 x, Int32 y)
at System.Windows.Forms.ContextMenuStrip.ShowInTaskbar(Int32 x, Int32 y)
at System.Windows.Forms.NotifyIcon.ShowContextMenu()
at System.Windows.Forms.NotifyIcon.WndProc(Message& msg)
at System.Windows.Forms.NotifyIcon.NotifyIconNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr
wparam, IntPtr lparam)
2009-11-24 10:47:41,609 [1] INFO Hudson.TrayTracker.Program -
HudsonTrayTracker
v0.9.6.0 Exit
2009-11-24 10:47:41,625 [1] ERROR Hudson.TrayTracker.Program - Win32Exception -
Error creating window handle.
2009-11-24 10:47:41,781 [1] ERROR Hudson.TrayTracker.Program - at
System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Form.CreateHandle()
at DevExpress.XtraEditors.XtraForm.CreateHandle()
at System.Windows.Forms.Control.get_Handle()
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at DevExpress.XtraEditors.XtraMessageBoxForm.DoShowDialog(IWin32Window owner)
at DevExpress.XtraEditors.XtraMessageBoxForm.ShowMessageBoxDialog()
at DevExpress.XtraEditors.XtraMessageBoxForm.ShowMessageBoxDialog
(XtraMessageBoxArgs message)
at DevExpress.XtraEditors.XtraMessageBox.Show(UserLookAndFeel lookAndFeel,
IWin32Window owner, String text, String caption, DialogResult[] buttons, Icon
icon,
Int32 defaultButton, MessageBoxIcon messageBeepSound)
at DevExpress.XtraEditors.XtraMessageBox.Show(IWin32Window owner, String text,
String caption, DialogResult[] buttons, Icon icon, Int32 defaultButton,
MessageBoxIcon messageBeepSound)
at DevExpress.XtraEditors.XtraMessageBox.Show(IWin32Window owner, String text,
String caption, MessageBoxButtons buttons, MessageBoxIcon icon,
MessageBoxDefaultButton defaultButton)
at DevExpress.XtraEditors.XtraMessageBox.Show(String text, String caption,
MessageBoxButtons buttons, MessageBoxIcon icon)
at Hudson.TrayTracker.Utils.ThreadExceptionHandler.HandleException(Exception ex)
at Hudson.TrayTracker.Utils.ThreadExceptionHandler.Application_ThreadException
(Object sender, ThreadExceptionEventArgs e)
at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
at System.Windows.Forms.NotifyIcon.NotifyIconNativeWindow.OnThreadException
(Exception e)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr
wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.PeekMessage(MSG& msg, HandleRef hwnd,
Int32 msgMin, Int32 msgMax, Int32 remove)
at
System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNat
iveMe
thods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason,
Int32
pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason,
ApplicationContext context)
at System.Windows.Forms.Application.Run(ApplicationContext context)
at Hudson.TrayTracker.Program.Main()
Original comment by par.toma...@gmail.com
on 24 Nov 2009 at 11:11
The debug version seems to work better? dont know why, but about 10 developers
have
their hudson tray tracker crashed everyday. we run multiple buildservers if
that
helps to any lead.
Have you been able to look anything at it?
Original comment by par.toma...@gmail.com
on 3 Dec 2009 at 10:27
Most people having the "Error creating window handle" error suggest looking at
the
number of handles owned by the program. You can display that in the process
explorer
by showing the "GDI objects" or "Handles" columns. It looks like there is a
limit of
10 000 handles for a process, but I cannot see HTT consuming more than 600
handles
and 150 GDI objects, and it does not seem to be growing. I will have another
look
tomorrow on my work computer.
Can let me know the number of GDI objects and handles is consummed on your
computer?
Thanks.
Original comment by Alexis.S...@gmail.com
on 3 Dec 2009 at 10:00
Also, another question: is the error always the same in the log files?
Thanks.
Original comment by Alexis.S...@gmail.com
on 3 Dec 2009 at 10:01
I think you should close this issue now since it hasn't been an issue since
almost a year ago. And none of us in our organisation has this issue, and since
i'm the reporter i think it should be closed.
Original comment by par.toma...@gmail.com
on 1 Dec 2010 at 2:40
Original issue reported on code.google.com by
par.toma...@gmail.com
on 20 Nov 2009 at 10:08