[Tickets #7063] Re: stack overflow in IE

bugs at horde.org bugs at horde.org
Thu Jul 24 18:29:44 UTC 2008


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7063
------------------------------------------------------------------------------
  Ticket             | 7063
  Updated By         | jbesko at msu.edu
  Summary            | stack overflow in IE
  Queue              | DIMP
  Version            | 1.0
  Type               | Bug
  State              | Stalled
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


jbesko at msu.edu (2008-07-24 14:29) wrote:

> I believe I found a way to reproduce it:

I wasn't able to reproduce the "Stack Overflow at line: 2" using your  
method, but
I was able to reproduce the error message with these steps:

1. Log in using Dynamic mode
2. Click on a message in my Inbox so I can preview the message
3. Click on another folder in the side bar (i.e. Sent or Trash)
4. The error pops up and message is unchecked
5. Click on the same folder, and I see the contents.

(note: the stack overflow message doesn't seem to cause any bad side
effects that I have noticed, just the annoying message pops up.)

This is only in IE (version 7.0 tested) on a Windows XP SP3 system.

When using Firefox v3.0, I don't get this behavior.  This is what happens
when I use Firefox 3 on the same WinXP SP3 system:

1. Log in using Dynamic mode
2. Click on a message in my Inbox so I can preview the message
3. Click on another folder in the side bar (i.e. Sent or Trash)
4. Message is unchecked, but I don't see contents of other folder
5. Click on the same folder, and I see the contents.

I have checked the behavior on Mac OS X v10.4.11 with Safari v3.1.2
and Firefox v3.0 and both Mac browsers behaved the same way
Firefox v3.0 behaved in WinXP SP3.

I also checked the behavior on OpenSuSE 10.3 and Firefox 2.0.0.15,
and it behaved the same as Firefox 3.0 in WinXP SP3.

I hope this helps.





More information about the bugs mailing list