[Bug 58757] New: Camerabag Pro 2025.2 crashes with unhandled exception (Unhandled exception: page fault on read access to 0x0000000000000000) when

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

Bug ID: 58757
           Summary: Camerabag Pro 2025.2 crashes with unhandled exception
                    (Unhandled exception: page fault on read access to
                    0x0000000000000000) when
           Product: Wine
           Version: 10.16
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: windowscodecs
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 79385
  --> http://bugs.winehq.org/attachment.cgi?id=79385
Sample image used to test this

New installation of Wine 10.16, new installation of CameraBag Pro 2025.2.

Without installing windowscodecs via vinetricks, before opening an image,
mouseover previews of an otherwise unseen sample image are displayed.

After opening an image, it knows the size etc of what it's been asked to open,
but the display of it is black. Similarly, the mouseover previews of the
various effects are black.

On saving, the file appears to be all black.

After installing windowscodecs via vinetricks, it displays the iamges and
mouseovers of it correctly. Saves are also correct.

https://web.archive.org/web/20250919105142/https://nevercenter.com/camerabag...
> $ du -h Install_CameraBag_Pro_2025_2_0_win.exe 
> 63M     Install_CameraBag_Pro_2025_2_0_win.exe
> $ sha1sum Install_CameraBag_Pro_2025_2_0_win.exe 
> 01d4daf1dd05ab426858e19191dbabfa855c2558  Install_CameraBag_Pro_2025_2_0_win.exe

[Bug 58757] Camerabag Pro 2025.2 crashes with unhandled exception (Unhandled exception: page fault on read access to 0x0000000000000000) when

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

--- Comment #1 from Nikolay Sivov  ---
Is the bug title wrong then? It talks about crashes, while description only
talks about image not being rendered.

Please attach +wincodecs wine log, as a text file.

[Bug 58757] Camerabag Pro 2025.2 crashes with unhandled exception (Unhandled exception: page fault on read access to 0x0000000000000000) when

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

--- Comment #2 from Ian  ---
Created attachment 79386
  --> http://bugs.winehq.org/attachment.cgi?id=79386
Saved sample image just in case it has useful info

[Bug 58757] Camerabag Pro 2025.2 fails to load image picture data unless winetricks windowscodecs used

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

Ian  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Camerabag Pro 2025.2        |Camerabag Pro 2025.2 fails
                   |crashes with unhandled      |to load image picture data
                   |exception (Unhandled        |unless winetricks
                   |exception: page fault on    |windowscodecs used
                   |read access to              |
                   |0x0000000000000000) when    |

[Bug 58757] Camerabag Pro 2025.2 fails to load image picture data unless winetricks windowscodecs used

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

--- Comment #3 from Ian  ---
(In reply to Nikolay Sivov from comment #1)
> Is the bug title wrong then? It talks about crashes, while description only
> talks about image not being rendered.

Yes, sorry, there's about three things to report and the wrong title was
pasted. Now edited.
> Please attach +wincodecs wine log, as a text file.

Attached has the results of running a plain Wine install with

env "WINEDEBUG=+windowscodecs"

.. is that what you're after?

[Bug 58757] Camerabag Pro 2025.2 fails to load image picture data unless winetricks windowscodecs used

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

--- Comment #4 from Ian  ---
Created attachment 79387
  --> http://bugs.winehq.org/attachment.cgi?id=79387
The result of running with env "WINEDEBUG=+windowscodecs"

[Bug 58757] Camerabag Pro 2025.2 fails to load image picture data unless winetricks windowscodecs used

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

--- Comment #5 from Nikolay Sivov  ---
(In reply to Ian from comment #3)
> Attached has the results of running a plain Wine install with
>
> env "WINEDEBUG=+windowscodecs"
>
> .. is that what you're after?

Yes, but correct name for it is WINEDEBUG=+wincodecs

[Bug 58757] Camerabag Pro 2025.2 fails to load image picture data unless winetricks windowscodecs used

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

Ian  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #79387|0                           |1
        is obsolete|                            |

--- Comment #6 from Ian  ---
Created attachment 79389
  --> http://bugs.winehq.org/attachment.cgi?id=79389
The result of running with env "WINEDEBUG=+wincodecs"

[Bug 58757] Camerabag Pro 2025.2 fails to load image picture data unless winetricks windowscodecs used

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

--- Comment #7 from Ian  ---
Thanks for the hand-holding.

As well as the lines showing things like reading EXIF data are not implemented,
there's one that sounds a likely candidate for this:

0128:fixme:wincodecs:copypixels_to_64bppRGBA Unimplemented conversion path 18.

[Bug 58757] Camerabag Pro 2025.2 fails to load image picture data unless winetricks windowscodecs used

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58757

--- Comment #8 from Nikolay Sivov  ---
Yes, that sounds important.

Regarding metadata, we have some support for metadata blocks of various types.
There is no support for XMP (xml-based metadata content), and also no support
for what's called "policy expressions", which is what happens in this log -
comma-separate names like System.Photo.xxxx. Presumably that gets translated to
a query, depending on metadata format.

Anyway, metadata support is unlikely an issue I think.