Jump to content
You must now use your email address to sign in [click for more info] ×

gkalab

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by gkalab

  1. I played around a bit and installed oclgrind, which is a "virtual OpenCL device simulator" and it is displayed as an additional OpenCL Hardware in Photo Beta. Together with oclgrind I was unable to reproduce the issue - I got no hang. Then I've uninstalled oclgrind and I can reproduce the hang on an empty pixel layer (it is more difficult to reproduce with actual image data). So maybe the UHD630 has to be the only graphics card installed to reproduce the issue? On a side note what's also interesting is that I don't get the 2 second lag when adding the first pixel layer on a new document after starting photo when oclgrind is installed. I do get the lag adding the first pixel layer after starting photo every time when oclgrind is not installed.
  2. The reports folder is empty. Maybe because the application hangs and does not crash any more (since the first beta or so)? Here are the Windows Event Viewer entries - unfortunately I only have a German Windows 10 version: 1) System log Warning 28.10.2020 21:38:41: Der Anzeigetreiber "igfx" reagiert nicht mehr und wurde wiederhergestellt. 2) Application Info 28.10.2020 21:38:43: Fehlerbucket , Typ 0 Ereignisname: LiveKernelEvent Antwort: Nicht verfügbar CAB-Datei-ID: 0 Problemsignatur: P1: 141 P2: ffff8905d7cab010 P3: fffff8060e524cb0 P4: 0 P5: 2ce4 P6: 10_0_19041 P7: 0_0 P8: 256_1 P9: P10: Angefügte Dateien: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201028-2138.dmp \\?\C:\WINDOWS\TEMP\WER-187532390-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F43.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F44.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F53.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F64.tmp.txt Diese Dateien befinden sich möglicherweise hier: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_85ea1efb85582c374233b5b5eb7df9b465ef758_00000000_b93c5b0b-f090-4298-9f4b-b958026937d8 Analysesymbol: Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: b93c5b0b-f090-4298-9f4b-b958026937d8 Berichtstatus: 4 Bucket mit Hash: CAB-Datei-Guid: 0 3) Application Info 28.10.2020 21:38:43: Fehlerbucket , Typ 0 Ereignisname: LiveKernelEvent Antwort: Nicht verfügbar CAB-Datei-ID: 0 Problemsignatur: P1: 141 P2: ffff8905d7cab010 P3: fffff8060e524cb0 P4: 0 P5: 2ce4 P6: 10_0_19041 P7: 0_0 P8: 256_1 P9: P10: Angefügte Dateien: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201028-2138.dmp \\?\C:\WINDOWS\TEMP\WER-187532390-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F43.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F44.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F53.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F64.tmp.txt Diese Dateien befinden sich möglicherweise hier: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_85ea1efb85582c374233b5b5eb7df9b465ef758_00000000_cab_b93c5b0b-f090-4298-9f4b-b958026937d8 Analysesymbol: Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: b93c5b0b-f090-4298-9f4b-b958026937d8 Berichtstatus: 2049 Bucket mit Hash: CAB-Datei-Guid: 0 -------------------- After closing the hanging app: 4) Application Error 28.10.2020 21:39:39 Das Programm Photo.exe Version 1.9.0.820 hat die Interaktion mit Windows beendet und wurde geschlossen. Überprüfen Sie den Problemverlauf in der Systemsteuerung "Sicherheit und Wartung", um nach weiteren Informationen zum Problem zu suchen. Prozess-ID: 2ce4 Startzeit: 01d6ad6a3e17f508 Beendigungszeit: 10 Anwendungspfad: C:\Program Files\Affinity\Photo Customer Beta\Photo.exe Bericht-ID: 64f2d917-e691-47b2-af95-879c9c984797 Vollständiger Name des fehlerhaften Pakets: Relative Anwendungs-ID des fehlerhaften Pakets: Absturztyp: Unknown 5) Application Info 28.10.2020 21:39:39 Fehlerbucket , Typ 0 Ereignisname: AppHangB1 Antwort: Nicht verfügbar CAB-Datei-ID: 0 Problemsignatur: P1: Photo.exe P2: 1.9.0.820 P3: 5f95f25f P4: 008a P5: 134217728 P6: P7: P8: P9: P10: Angefügte Dateien: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5514.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5534.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5535.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5546.tmp.txt \\?\C:\Users\Gerhard\AppData\Local\Temp\WER6840.tmp.appcompat.txt Diese Dateien befinden sich möglicherweise hier: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Photo.exe_78b7bbace0373c4ca77c2cd0f8ae6f4635367c47_a854876b_7852583e-4b3c-4d98-b16c-e76cd4dc5a25 Analysesymbol: Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: 64f2d917-e691-47b2-af95-879c9c984797 Berichtstatus: 1 Bucket mit Hash: CAB-Datei-Guid: 0 ------------------ The folder C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Photo.exe_78b7bbace0373c4ca77c2cd0f8ae6f4635367c47_a854876b_7852583e-4b3c-4d98-b16c-e76cd4dc5a25 contained a Report.wer file, which I have attached. Report.wer
  3. Thank you for trying 🙂 I'm wondering: are you trying to reproduce this issue on an Intel 630UHD graphics card? If not, maybe that's the reason you are failing to reproduce the issue? Also, is there really no log file the applicaction is writing in the debug version?
  4. It's constant dragging without release. Most of the time the program is just hanging - see thread list. Yes, it seems one core is a little busy. BTW, while dragging it's always the clReleaseGlSharedEvent thread that's on the top. Attached are the CPU graph, GPU graph and thread list when the program hangs. The GPU spike is from when I was constantly dragging.
  5. Well - there is no history except creating a new pixel layer 🙂 - but I saved a file for you. It takes me about half a minute dragging the slider left and right to make the application hang. Again the steps I took to reproduce the issue: - Create a new document (I chose 800x600) - Create a new empty pixel layer - This time I saved the document to the attached file. - Choose from the menu: Select sampled color - Drag the slider for one minute or so. This time there's also an autosave file (attached). Thank you. example.afphoto 20201001145628.autosave
  6. There are no crash reports in C:\Users\<usernam>\AppData\Roaming\Affinity\Photo\1.0 (Beta)\CrashReports. Is there any other log file I can send? I can still reproduce the issue with the latest beta (1.9.0.767). It seems it is now harder to reproduce (don't know why): now I need to move the slider several times forth and back as @Joachim_L mentioned. Most of the time the application just hangs and I have to kill it, sometimes it crashes. I made sure I installed the latest graphic drivers from Intel: Processor: Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz, Graphics card: on-board Intel(R) UHD Graphics 630UHD
  7. Beta 1.9.0.734 crashes or hangs the process when you increase the tolerance when selecting a sampled color. This only happens when OpenCL is enabled. Steps to reproduce: Create a new document Create a new empty pixel layer Select sampled color Increase the tolerance
  8. Similar to a different request for offering the original source folder for exports as default, I'd like to request default folders for filters, etc. The current handling of default locations in the folder selection panel is awkward. When I do the following steps: select a LUT file for a LUT adjustment layer from a LUT resources folder export -> the export dialog panel offers the previous LUT file folder which means that I need to browse again to an export folder filter - apply image -> the previously selected export folder is offered and I need to browse to my image resources folder change the LUT file of the LUT adjustment layer from the first step: now the previously selected image resources folder is offered and again I need to go through the filesystem to my LUT resources folder My request: remember the last used folder for each filter type (LUT adjustment layer, apply image) use the original source folder for save selection, load selection from file use the last "Open..." folder for the "add" files dialog in "New Panorama", "New Stack", "New HDR Merge", "New Focus Merge"
  9. A little off topic but the question comes up wether an Android version is planned?
  10. Do you have any brushes installed? I had to reset the brushes in the previous beta before installing the new one - see my post above.
  11. 1.5.1.51 beta was constantly crashing on startup for me installed before: 1.5.1.47 beta DAUB Blenders.afbrushes DAUB Concept Tools PRO.afbrushes setting: English language (instead of German) this worked for me: - remove 1.5.1.51 - install previous beta (1.5.1.47) - reset brushes (brushes get removed and there's an error message) - reset user defaults - remove beta 1.5.1.47 - install 1.5.1.51 Now it seems to work fine.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.