Crash when hovering over image in Box Drive folder

Things you’d like to miss in the future...
Post Reply
oblivion
Posts: 142
Joined: 13 Apr 2011 11:35

Crash when hovering over image in Box Drive folder

Post by oblivion »

Couple of crashes this morning -- XYplorer just goes away with no apparent errors when I hover over a jpg in a cloud folder, using Box Drive.

And it could just as easily be a problem with the Box Drive application, I grant :)

Error log shows:

Log Name: Application
Source: Application Error
Date: 07/09/2022 09:25:18
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-37OIGSF
Description:
Faulting application name: XYplorer.exe, version: 23.60.0.0, time stamp: 0x63122306
Faulting module name: BoxShellExt32-2.27.242.dll, version: 2.27.242.0, time stamp: 0x62d9c4cd
Exception code: 0xc0000005
Fault offset: 0x00029369
Faulting process ID: 0x35c4
Faulting application start time: 0x01d8c2907230e5ab
Faulting application path: x:\xxxxxxxxxxxx\XYPlorer\XYplorer.exe
Faulting module path: x:\Program Files\Box\Box\BoxShellExt32-2.27.242.dll
Report ID: 6704662e-3ac4-4003-9ab4-3c8f420f50b1
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-09-07T08:25:18.5397651Z" />
<EventRecordID>105043</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>computername</Computer>
<Security />
</System>
<EventData>
<Data>XYplorer.exe</Data>
<Data>23.60.0.0</Data>
<Data>63122306</Data>
<Data>BoxShellExt32-2.27.242.dll</Data>
<Data>2.27.242.0</Data>
<Data>62d9c4cd</Data>
<Data>c0000005</Data>
<Data>00029369</Data>
<Data>35c4</Data>
<Data>01d8c2907230e5ab</Data>
<Data>x:\xxxxxxxxxxxx\XYPlorer\XYplorer.exe</Data>
<Data>x:\Program Files\Box\Box\BoxShellExt32-2.27.242.dll</Data>
<Data>6704662e-3ac4-4003-9ab4-3c8f420f50b1</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
-- bests, Tim

...This space unintentionally left blank.

admin
Site Admin
Posts: 60635
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Crash when hovering over image in Box Drive folder

Post by admin »

Try the same with v23.60.0004.

oblivion
Posts: 142
Joined: 13 Apr 2011 11:35

Re: Crash when hovering over image in Box Drive folder

Post by oblivion »

admin wrote: 07 Sep 2022 11:48 Try the same with v23.60.0004.
I've just tried it with .0005 and it's worked perfectly :D thanks!
-- bests, Tim

...This space unintentionally left blank.

admin
Site Admin
Posts: 60635
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Crash when hovering over image in Box Drive folder

Post by admin »

I did not fix anything, I just added debug code.

oblivion
Posts: 142
Joined: 13 Apr 2011 11:35

Re: Crash when hovering over image in Box Drive folder

Post by oblivion »

Ah. :)

I think the problem was kind of network related -- I was using the laptop with a hotspot provided by my phone and I discovered a bit later that the automatic mirroring of files between the folder on the laptop I was actually looking at and the Box-hosted files themselves weren't fully in sync. So the files appeared to be present but -- I think -- the content was still being transferred. (I was using a VPN pointed at a server that, while it looked effective, was actually cutting download speeds to glacially slow...)

So definitely not XYplorer's fault, in that sense, although the addition of debug code might help the development of an error trap if it happens again, I guess?
-- bests, Tim

...This space unintentionally left blank.

admin
Site Admin
Posts: 60635
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Crash when hovering over image in Box Drive folder

Post by admin »

You should try to make it happen with 23.60.0004. There should come a helpful error message right before the crash.

Post Reply