#223 Unable to complete backup

closed
nobody
None
2012-11-24
2012-11-13
Paolo
No

Run v.5.10Beta, after 4 hours it was about half set, 4.12% in size, cpu load was 99% and copy speed almost 0; in next 4 hours it copied 2 more files.
After rechecking Task Manager I killed FFS, so I can't send you a memory dump.
I can run again FFS and get a memdump when it freeze if you send me a appl to get it.
Links:
http://imageshack.us/photo/my-images/525/freefilesyncv510betaerr.jpg/
http://imageshack.us/photo/my-images/713/freefilesyncv510betaerr.jpg/

1 Attachments

Discussion

1 2 > >> (Page 1 of 2)
  • Zenju
    Zenju
    2012-11-14

    This must be something unrelated to the changes due to the out of memory problem.
    Next time this happens, don't kill the app, but open task manager, right-click and create a process dump.
    Or for that purpose I would suggest to use Process Explorer instead of the default Windows task manager, select the hanging FFS process, right-click -> "create dump" -> "Create minidump"
    Creating memory dumps this way of course only works with the special FFS version you already have, not with a regular FFS version.

     
  • Zenju
    Zenju
    2012-11-14

    One more thing:
    It is possible that the minidump file is corrupted and I cannot read it. As a fallback I can try to reconstruct what is happending if I have the call stack.

    This is exactly what happened in this case:
    https://sourceforge.net/p/freefilesync/discussion/help/thread/c7df0d13

    So please also include the call stack for the FFS main thread:

    go into process explorer, lookup FreeFileSync_x32.exe properties, goto Threads tab, and click "stack" with the main thread selected (FreeFileSync_x32.exe!WinMainCRTStartup). Click "Copy All" and report the call stack. This will be poor man's debugging, but at least I should be able to see where the error occurs.

     
    Last edit: Zenju 2013-06-13
  • Paolo
    Paolo
    2012-11-15

    Tonight I run v.5.10Beta, when it was about half set, this time 4.20% in size, maximum cpu load and copy speed almost 0.
    I was not able to identify FreeFileSync_x32.exe!WinMainCRTStartup, but
    - the 1st thread stack was:
    ntkrnlpa.exe+0x6a9bf
    FreeFileSync_Win32.exe+0x1f5b9
    FreeFileSync_Win32.exe+0x7ce34
    FreeFileSync_Win32.exe+0x823dd
    FreeFileSync_Win32.exe+0x81e26
    FreeFileSync_Win32.exe+0x800e9
    FreeFileSync_Win32.exe+0x7cf54
    FreeFileSync_Win32.exe+0x7df04
    FreeFileSync_Win32.exe+0x7e961
    FreeFileSync_Win32.exe+0x1044a4
    FreeFileSync_Win32.exe+0x2b031d
    FreeFileSync_Win32.exe+0x2b1024
    FreeFileSync_Win32.exe+0x2b11f5
    FreeFileSync_Win32.exe+0x2b15c8
    FreeFileSync_Win32.exe+0x25b160
    FreeFileSync_Win32.exe+0x25b4f7
    USER32.dll+0x8734
    USER32.dll+0x8816
    USER32.dll+0x89cd
    USER32.dll+0x8a10
    USER32.dll+0x174ff
    FreeFileSync_Win32.exe+0x2811d4
    FreeFileSync_Win32.exe+0x280e9f
    FreeFileSync_Win32.exe+0x281147
    FreeFileSync_Win32.exe+0x22d731
    FreeFileSync_Win32.exe+0xc4ffb
    FreeFileSync_Win32.exe+0x1a7670
    FreeFileSync_Win32.exe+0x1a9153
    FreeFileSync_Win32.exe+0x1690d2
    FreeFileSync_Win32.exe+0xf5cf0
    FreeFileSync_Win32.exe+0xe5650
    FreeFileSync_Win32.exe+0x1eaaec
    kernel32.dll+0x2827c
    kernel32.dll+0x27a05
    kernel32.dll+0x27b6b
    FreeFileSync_Win32.exe+0x1eacf8
    FreeFileSync_Win32.exe+0x1eb635
    FreeFileSync_Win32.exe+0x1eb6c8
    FreeFileSync_Win32.exe+0x1eb8c8
    FreeFileSync_Win32.exe+0x1eb962
    FreeFileSync_Win32.exe+0xe513f
    FreeFileSync_Win32.exe+0xe4214
    FreeFileSync_Win32.exe+0xde92c
    FreeFileSync_Win32.exe+0xd5eef
    FreeFileSync_Win32.exe+0xe1f3a
    FreeFileSync_Win32.exe+0xe4b0b
    FreeFileSync_Win32.exe+0xe190e
    FreeFileSync_Win32.exe+0xe5cc5
    FreeFileSync_Win32.exe+0xe34f9
    FreeFileSync_Win32.exe+0xdda2d
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xe19d7
    FreeFileSync_Win32.exe+0xe5d65
    FreeFileSync_Win32.exe+0xe3599
    FreeFileSync_Win32.exe+0xddabb
    FreeFileSync_Win32.exe+0xd555b
    FreeFileSync_Win32.exe+0xd8244
    FreeFileSync_Win32.exe+0x181a59
    FreeFileSync_Win32.exe+0x2b031d
    FreeFileSync_Win32.exe+0x2b1024
    FreeFileSync_Win32.exe+0x2b11f5
    FreeFileSync_Win32.exe+0x2b15c8
    FreeFileSync_Win32.exe+0x26aa80
    FreeFileSync_Win32.exe+0x26aae0
    FreeFileSync_Win32.exe+0x24438c
    FreeFileSync_Win32.exe+0x247771

    • the 2nd thread stack was:
      ntkrnlpa.exe+0x6a8bf
      ntkrnlpa.exe+0xf7126
      ntdll.dll+0xe514
      FreeFileSync_Win32.exe+0x1f837
      FreeFileSync_Win32.exe+0x26480
      FreeFileSync_Win32.exe+0x361f1
      FreeFileSync_Win32.exe+0x2fe8c
      FreeFileSync_Win32.exe+0x80a49
      FreeFileSync_Win32.exe+0x7de40
      FreeFileSync_Win32.exe+0x7e244
      FreeFileSync_Win32.exe+0x82312
      FreeFileSync_Win32.exe+0x324125
      FreeFileSync_Win32.exe+0x304a49
      FreeFileSync_Win32.exe+0x304ad3
      kernel32.dll+0xb729

    • the 3rd thread stack was:
      ntkrnlpa.exe+0x6a8bf
      ntkrnlpa.exe+0xf7126
      ntkrnlpa.exe+0x26b0b
      ntkrnlpa.exe+0x29d1e
      ntkrnlpa.exe+0xdf5d6
      ntkrnlpa.exe+0x66738
      ntdll.dll+0xe514
      kernel32.dll+0xa115
      FreeFileSync_Win32.exe+0x325148

    I enclose the minidump too.

     
  • Zenju
    Zenju
    2012-11-15

    Great, the memory dump is valid! I'm analyzing it...
    If the same or similar problems occurs, please send me more dump files, this would be a great help. Especially considering that the symptoms are not stable, as you describe 0% cpu load in one case, 100% in the other.

     
  • Zenju
    Zenju
    2012-11-15

    One additional question about what you are seeing: So is FFS hanging, i.e it is not responding to your input requests, for example when you are trying to cancel, or is it still "working", but just incredibly slow?

     
  • Paolo
    Paolo
    2012-11-15

    Sorry for unprecise description; symptoms was the same both the times: FFs was loading cpu about 100%.
    Previous time I monitored cpu activity with SIV32, it was average 100% busy, about 60% kernel and 40% user (see attach).
    -Continue...

     
  • Paolo
    Paolo
    2012-11-15

    • ...Continued
      This morning I was able to abort execution clicking FFS button "Annulla", so it was not hanging - it seems progressively slowing/stopping copying activity (Speed: few bytes/sec or "-", Time to Complete Syncro: tens-thousand days or "-"); I enclose the log printscreen.
      It make non-sense for me to execute FFS many hours to backup only a small part of the data set, but if you need more dump data I'll do it; please let me know about it, otherwise I'll wait a new release to test.
     
  • Zenju
    Zenju
    2012-11-15

    Yes, please send me more of them :) There's no need to reproduce this situation multiple times. The next time this problem occurs create multiple .dmp files via process explorer direcly one after the other, with only a few seconds in between them. FFS is still running while these memory dumps are created, so having multiple files will expose what are statistical effects only.

     
  • Paolo
    Paolo
    2012-11-16

    I know it's like asking to the wolf, but aren't there any security issues for me & my PC to send you all these dumps? All the people looking at this forum can access them...

     
  • Zenju
    Zenju
    2012-11-16

    All the passwords and email addresses I find in the memory dump, are in perfectly good hands! ;)

    But seriously; the dump files include parts of the FFS process memory only, so there isn't something interesting except for maybe file names at most.

     
1 2 > >> (Page 1 of 2)