Hey Daniel,
2014-04-09 17:59 GMT+02:00 Daniel Horsey <[email protected]>:
> 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?
>
Unfortunately, as the saying goes, with IE everything is possible. I would
suspect that the problem is not so much IE local versus remote, but rather
a problem with the the instance of IE that is installed locally ?
Perhaps the local IE browser has enabled some debugging features that
require it to keep all past state in memory? Just guessing, really.
Regards,
koen
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
