Details | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 466 | daniel-mar | 1 | |
| 2 | * FF 1.6 works with 10.000x10.000 picture and is fast. FF 1.7 shows not enough RAM, and if maxspace_availabe() is disabled, then it shows with 4 channels "Could not build preview at chosen zoom level." (e == memFullErr , needall=1). Also it is slow if it works with 3 channels. |
||
| 3 | R put(255-(min(min(r,g),b)),0),(c+get(0)-255)*255/get(0) |
||
| 4 | G (c+get(0)-255)*255/get(0) |
||
| 5 | B (c+get(0)-255)*255/get(0) |
||
| 6 | A get(0) |
||
| 7 | ==> Speed is OK if built with Visual Studio optimization |
||
| 8 | - todo: check if watcom is also fast |
||
| 9 | - todo: check if visual studio cli ist also fast |
||
| 10 | - do also need needall=0 (state changing functions)? |
||
| 11 | ==> RAM problem persists |
||
| 12 | abbruch bei (e = pb->advanceState() , OHNE dass dabei irgendwas aufgerufen wird. scheinbar beim ersten advancestate, danach keine breakpoints! |
||
| 13 | maxspace = 845934385 = 806 MB |
||
| 14 | ==> simple r,g,b,a Filter mit 4 channels |
||
| 15 | SVN rev 236 no mem problem |
||
| 16 | 269 no mem problem |
||
| 17 | 346 no mem problem |
||
| 18 | 384 am 1.11 no mem problem |
||
| 19 | 392 no mem problem!!! |
||
| 20 | ==> Grund: wenn ich maxspace() verwende, dann ist es in der tat BESSER, denn ich gebe wahrscheinlich mehr speicher als photoshop selbst geben würde! |
||
| 21 | ==> Peel of white filter |
||
| 22 | FF 1.6 zoomed in preview ist ok, ganze verarbeitung no ram |
||
| 23 | ===> jetzt geht's plötzlich doch??? und ganz schnell! |
||
| 24 | FF 1.7 zoomed out preview no ram, ganze verarbeitung no ram |
||
| 25 | selbst zoom auf 100% bringt nix |
||
| 26 | => weil needall=1 aufgrund von statechanging_vars_used=1? |
||
| 27 | auch ändern auf r,g,b,a bringt nix |
||
| 28 | => wenn er einmal im fehlerzustand ist, geht nix mehr weiter. RAM dann voll??? rauszoomen bringt dann auch nix! |
||
| 29 | mit state_changing_vars_used=0 geht es! |
||
| 30 | ===> danach plötzlich wieder doch nicht!!!!! |
||
| 31 | ==> RAM und geschwindigkeit mit 1.7.0.12 win64 photoshop cc nicht problematisch |
||
| 32 | |||
| 33 | * After working with Filter Foundry for a short amount of time (working with sliders, applying, opening again, changing sliders, etc.), the file save dialog (Make dialog) will corrupt the memory!!! You notice it by seeing that icons and folder icons are missing! Later, the program might even crash! (Verified with 1.7.0.12, verified with Visual Studio and OpenWatcom) Application Verifier does not report anything bad. |
||
| 34 | You can also corrupt the memory by often applying filters and building and doing stuff. And at some point you get the error that preview cannot be shown because memory is out??? |
||
| 35 | Do we have a leak??? |
||
| 36 | Smashing Ctrl+F does NOT cause a leak. |
||
| 37 | "Deleaker" tool only showed small leaks, nothing very big and no leaks with high hit-count! |
||
| 38 | ==> nein! ist eine unverträglichkeit mit application verifier! out of memory kommt auch ohne ffac |