search

rainbowcreatures / FlashyWrappers

AIR / Flash video recording SDK
17 stars 10 forks source link

Desktop: ADL Stopped working when recording starts in widows 64 #39

Open jkpatel1463 opened 6 years ago

jkpatel1463 commented 6 years ago

Hello @rainbowcreatures

The desktop app crashed when start recording. Here is the log file from documents: https://www.dropbox.com/s/dkz7gkkk4im1003/FW_log_28_spet_2017.txt?dl=0

Please message me if you need more information.

rainbowcreatures commented 6 years ago

Strange, Windows should be pretty much stable. I can't identify the crash place from the log, it seems a mashup of multiple sessions. Can you delete the logfile and reproduce the crash? Also, can you reproduce the crash everytime, is it rare etc.

I'd also appreciate a code sample / project and more specific Windows version than 64-bit (7,8,10)? I can try to run it on virtual machine here in case its anything other than 10.

jkpatel1463 commented 6 years ago

Hello @rainbowcreatures

Right now, i removed FlashyWrapper from Desktop app & used FFMPEG instead. so, it will take more times to revert the code, and produced the error again. I can give you a video's link which is generated from Windows 7-64bit os, so that you can identify the issues. https://www.dropbox.com/s/8j46czlad3ncp2c/15064301539730_vid.mp4?dl=0

Here are the issues, which i face while generating video in Windows 7, 64 bit:

  1. ADL consumes lots of memory
  2. So meanwhile release memory, ADL framerate drops,
  3. After release memory, again, ADL works with better framerate
  4. After consuming certain amount of memory, it crashes. Above 4 steps, happens(occurred) only first time. From second time onward, ADL Stopped working after 3 to 4 frame has been played. then i file a bug here with link of crashlog.
rainbowcreatures commented 6 years ago

Hi @jkpatel1463 , I'm not sure I understand fully about your memory issues.

Any Windows issue can be fixed pretty quickly(unlike Android), I've got Windows 7 virtual machine.

Are you saying there is a memory leak in FW when recording on Windows (growing memory)? Or is the memory growing within your app?

I'm going to e-mail you a debug version of FW for Windows. Please build your app with that, then send the app to me, including steps to reproduce your crash in the most straightforward way. I can launch your AIR app here, attach MSVC debugger and see whats going on inside my ANE just before the crash.

jkpatel1463 commented 6 years ago

Hello @rainbowcreatures

Any Windows issue can be fixed pretty quickly(unlike Android), I've got Windows 7 virtual machine. I removed Flashywrapper for Windows Desktop release and integrate FFMPEG successfully, created a video and deliver release as well. So Reproduce issues in windows takes more time. Now I am solving the issues of android. So I can give you log of it faster.

Are you saying there is a memory leak in FW when recording on Windows (growing memory)? Or is the memory growing within your app? If its memory leak then consumed memory will not recover afterward. but Its recovering consumed memory. Its working like

  1. at some time it has about 2GB of ram
  2. After release a memory it has 500MB of ram same steps happen again and again.

I noted this by taking a look at Task manager, i found that GC called and release a memory then again consuming memory, again releasing a memory, so it do not impress user, so integrated FFMPEG.

Bottomline: Generating Windows logs needs more time for me now, but when time permits, i will do. I can give you log for android now.

Thank you for preparing Debug release. I will submit log surely.

rainbowcreatures commented 6 years ago

k lets focus on Android then.