<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Document suddenly has a massive RAM spike in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537005#M1270542</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are using Windows Schedular ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Jul 2013 03:51:38 GMT</pubDate>
    <dc:creator>vikasmahajan</dc:creator>
    <dc:date>2013-07-30T03:51:38Z</dc:date>
    <item>
      <title>Document suddenly has a massive RAM spike</title>
      <link>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537004#M1270538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One of my documents has started using an extreme amount of RAM and I can't figure out why.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The document is about 250Mb and with one user logged onto it the server RAM usage suddenly spirals up to 90gb and results in a "No connection" error. The server is ONLY used for qlikview. Any ideas what this could be?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537004#M1270538</guid>
      <dc:creator />
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Document suddenly has a massive RAM spike</title>
      <link>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537005#M1270542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are using Windows Schedular ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jul 2013 03:51:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537005#M1270542</guid>
      <dc:creator>vikasmahajan</dc:creator>
      <dc:date>2013-07-30T03:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Document suddenly has a massive RAM spike</title>
      <link>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537006#M1270544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, no, Windows Scheduler is not currently running on my servers. I was able to somewhat remedy the situation by ending QVS.exe and letting it automatically restart. After that it stopped at 3gb. Further testing does show that QVS.exe still shoots up to about 90gb when it is first loaded from a full server restart though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will also add that when doing and development work on this document QV.exe similarly shoots up to 90gb or so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jul 2013 03:55:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537006#M1270544</guid>
      <dc:creator />
      <dc:date>2013-07-30T03:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: Document suddenly has a massive RAM spike</title>
      <link>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537007#M1270546</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have to Try to Re-install the Qlikview ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jul 2013 04:02:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537007#M1270546</guid>
      <dc:creator>vikasmahajan</dc:creator>
      <dc:date>2013-07-30T04:02:31Z</dc:date>
    </item>
    <item>
      <title>Re: Document suddenly has a massive RAM spike</title>
      <link>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537008#M1270548</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would think that something is messed up with the .share file for one of your documents.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1&amp;nbsp; Restart QVS and one one document at a time till you find the one causing the issue. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 Then stop QVS and rename the .share file for the one causing the issue and try again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bill&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jul 2013 12:06:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537008#M1270548</guid>
      <dc:creator>Bill_Britt</dc:creator>
      <dc:date>2013-07-31T12:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: Document suddenly has a massive RAM spike</title>
      <link>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537009#M1270550</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the tip. It could just be the size of the data and perhaps the organisation/number of tables I have in the document. In total running about 10,000 columns and roughly 250,000 rows :S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Aug 2013 10:37:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Document-suddenly-has-a-massive-RAM-spike/m-p/537009#M1270550</guid>
      <dc:creator />
      <dc:date>2013-08-01T10:37:08Z</dc:date>
    </item>
  </channel>
</rss>

