Hi Koen:
I've finally found an opportunity to troubleshoot this. The test case
confirmed that there is noting inherently wrong with Tableview.
The problem actually appears to be related to my test configuration: The
browser and the witty front end are running on the same platform. When
running the browser from a different machine everything works normally.
When I run it on the same machine, I see IE start to gobble up memory (~4-8k
per second) as soon as the witty code is started (when I get to the login
screen) - you can almost set your watch by it. This continues after
navigation away from the page, until the browser tab where witty was is
closed. This does not occur when a remote machine is running IE.
Is it possible that the browser is running out of memory in this
configuration? Obviously, the system would never be deployed like this, but
the behavior is curious. Any ideas on what's happening here?
Best,
-dan
_____
From: Daniel Horsey [mailto:dan.hor...@broadruntech.com]
Sent: Saturday, February 08, 2014 9:43 AM
To: 'witty-interest@lists.sourceforge.net'
Subject: Re: IE9 tableview error
>Hey Daniel,
>
>Actually the problem we saw is specific to table, not tableview. Any chance
of being able to reproduce this in a test case?
>What version of Wt do you see this with?
>
>Regards,
>Koen"
Hi Koen:
Yes, I will try to put a test case together, but it will take a while, as
I'm up to my eyeballs right now. The Wt version I am on is 3.3.0.
BR,
-dan
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
