Logo by Maya - Contribute your own Logo!

END OF AN ERA, FRACTALFORUMS.COM IS CONTINUED ON FRACTALFORUMS.ORG

it was a great time but no longer maintainable by c.Kleinhuis contact him for any data retrieval,
thanks and see you perhaps in 10 years again

this forum will stay online for reference
News: Did you know ? you can use LaTex inside Postings on fractalforums.com!
 
*
Welcome, Guest. Please login or register. March 28, 2024, 03:04:59 PM


Login with username, password and session length


The All New FractalForums is now in Public Beta Testing! Visit FractalForums.org and check it out!


Pages: 1 [2]   Go Down
  Print  
Share this topic on DiggShare this topic on FacebookShare this topic on GoogleShare this topic on RedditShare this topic on StumbleUponShare this topic on Twitter
Author Topic: 2.08-3 Constant Crashing - "No Symbol file loaded"'  (Read 2751 times)
Description: info gleaned from Visual Studio 2015 'debug'
0 Members and 1 Guest are viewing this topic.
Buddhi
Fractal Iambus
***
Posts: 895



WWW
« Reply #15 on: September 08, 2016, 09:40:02 PM »

Today I have found the error which probably caused crashing of the application. Using valgrind memory checker tool I have try to do different things with the program. I was very long process (program runs 100 times slower than normally), but I have finally generated and logged crash of the program. When the problem window was being resized then image preview was also resized (freeing and allocating of memory) and at the same time image preview was updated by rendering thread. It caused writing the data to memory which was no longer allocated.
I have fixed the problem using QMutex which prevents from reallocating of memory during updating of preview. Now I cannot crash the program in the same way.
Logged

knighty
Fractal Iambus
***
Posts: 819


« Reply #16 on: September 08, 2016, 10:16:49 PM »

Why not just avoid reallocation? isn't it "better" to allocate a sufficient amount of memory for all cases at the beginning?
Logged
Buddhi
Fractal Iambus
***
Posts: 895



WWW
« Reply #17 on: September 10, 2016, 09:13:14 AM »

Why not just avoid reallocation? isn't it "better" to allocate a sufficient amount of memory for all cases at the beginning?

It's not possible in this case until image preview resolution can be different and zoom in the window also can be changed. Going in that way the program should allocate RGB8 bitmap for 65636x65536x400% bitmap. It's not reasonable smiley
Logged

Pages: 1 [2]   Go Down
  Print  
 
Jump to:  


Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM
Page created in 0.146 seconds with 26 queries. (Pretty URLs adds 0.008s, 2q)