Open markcmiller86 opened 5 years ago
This is even worse for other datasets. I'm trying to generate a simple shock tube movie, and, around frame 150, my entire laptop freezes and needs to be restarted. I have two plots—one pseudocolor and one filled boundary—and a single transform operator.
@aowen87 did you watch with Activity Monitor to see if you noticed anything unusual there?
Unfortunately, no. I would have started to had I still been able to control my mouse. I can try repeating this again with the monitor up, but I'd prefer to wait until the end of the day so that I don't lose all of my sessions again.
Okay, I just ran it again but only saved 50 frames. About halfway through, VisIt's viewer becomes unresponsive. It did complete, though.
Any memory/stack issues?
-- Kevin
From: Alister notifications@github.com Reply-To: visit-dav/visit reply@reply.github.com Date: Wednesday, April 8, 2020 at 10:56 AM To: visit-dav/visit visit@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [visit-dav/visit] Save movie with 3-slice template hits a wall (#3802)
Okay, I just ran it again but only saved 50 frames. About halfway through, VisIt's viewer becomes unresponsive. It did complete, though. [Screen Shot 2020-04-08 at 10 52 00 AM]https://user-images.githubusercontent.com/11658578/78817046-6c22fe80-7987-11ea-9304-6f704bbc1694.png
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/visit-dav/visit/issues/3802#issuecomment-611102950, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGMIKBMCJDTQ4U5S2QBKRWDRLS3FZANCNFSM4IOZWZ5Q.
Memory looks similar. This was after saving ~70 images.
Describe the bug
90% way through creation of a movie, performance bogs down to a crawl. It is chuging along at about 1 frame/sec save rate and then at the end, it takes forever for each frame to render.
To Reproduce
wave_smaller.visit
(see below).I don't think the specific file matters but here is what I was using...
This is happening on 3.0.1. I have observed on OSX. I haven't tried any other OS.
I check performance monitor and don't see any memory, cpu or networking oddities.