Camera Access issue #1323
Comments
|
Notes: This is now occurring on a 2.3 GHz Dual-Core Intel Core i5 Macbook Pro for Sparrow-1.8.2-x86_64 and Sparrow-1.8.4-x86_64 when trying to read from the camera during XPUB key import. Translated Report (Full Report Below)Process: Sparrow [4363] Date/Time: 2024-03-16 13:01:34.2695 -0500 Sleep/Wake UUID: 2256026F-EF9D-49AD-9F67-56FEE76659A7 Time Awake Since Boot: 24000 seconds System Integrity Protection: enabled Crashed Thread: 75 Java: atomic-processor-1 Exception Type: EXC_BAD_ACCESS (SIGABRT) Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 VM Region Info: 0xb4 is not in any region. Bytes before following region: 140737486618444 Application Specific Information: Thread 0:: Dispatch queue: com.apple.main-thread Model: MacBookPro14,1, BootROM 526.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 2.3 GHz, 8 GB, SMC 2.43f11 |
|
Thanks for the bug report. It looks similar to #1215. Are you able to find the same problematic stack in #1215 (comment) in the Java Unfortunately I haven't been able to reproduce this somewhat rare issue myself, but I'm starting to get enough information to report the bug on the OpenIMAJ driver. Any help narrowing this down would be much appreciated. |
|
I also have an idea this bug might be avoidable by changing the value of |
|
Great idea! I'll rebuild from source and let you know.
Thank you so much! I love my SparrowWallet!
…On Sun, Mar 17, 2024, 4:06 AM craigraw ***@***.***> wrote:
I also have an idea this bug might be avoidable by changing the value of
SCAN_LOOP_WAIT_MILLIS in WebcamScanDevice
<https://github.com/sparrowwallet/sparrow/blob/master/src/main/java/com/sparrowwallet/sparrow/control/WebcamScanDevice.java>.
If you run from source (instructions in the project README) changing this
value to a higher number might reduce the scan interval sufficiently that a
thread race problem does not occur.
—
Reply to this email directly, view it on GitHub
<#1323 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF5MIDWX3BC2CKPLUALYYGLYYVMKJAVCNFSM6AAAAABEZQDJXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGM3TEMJXGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I built and ran Sparrow using temurin-18 jdk and jre.
Wallets load great.
Import wallet using camera breaks.
hs_err_pid10958.log attached here.
On Sun, Mar 17, 2024 at 12:33 PM Brian Jeffreys ***@***.***>
wrote:
… Great idea! I'll rebuild from source and let you know.
Thank you so much! I love my SparrowWallet!
On Sun, Mar 17, 2024, 4:06 AM craigraw ***@***.***> wrote:
> I also have an idea this bug might be avoidable by changing the value of
> SCAN_LOOP_WAIT_MILLIS in WebcamScanDevice
> <https://github.com/sparrowwallet/sparrow/blob/master/src/main/java/com/sparrowwallet/sparrow/control/WebcamScanDevice.java>.
> If you run from source (instructions in the project README) changing this
> value to a higher number might reduce the scan interval sufficiently that a
> thread race problem does not occur.
>
> —
> Reply to this email directly, view it on GitHub
> <#1323 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AF5MIDWX3BC2CKPLUALYYGLYYVMKJAVCNFSM6AAAAABEZQDJXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGM3TEMJXGA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
I tried bumping up SCAN_LOOP_WAIT_MILLIS to 500 and then 2500, but same
result.
I can tell you that I've been using Sparrow Wallet for a long time now on
this machine, so I am suspecting that my camera is dying or the driver has
changed.
But thank you for trying to help!
(I love open source software!)
public static final int SCAN_LOOP_WAIT_MILLIS = 2500;
…On Sun, Mar 17, 2024 at 4:06 AM craigraw ***@***.***> wrote:
I also have an idea this bug might be avoidable by changing the value of
SCAN_LOOP_WAIT_MILLIS in WebcamScanDevice
<https://github.com/sparrowwallet/sparrow/blob/master/src/main/java/com/sparrowwallet/sparrow/control/WebcamScanDevice.java>.
If you run from source (instructions in the project README) changing this
value to a higher number might reduce the scan interval sufficiently that a
thread race problem does not occur.
—
Reply to this email directly, view it on GitHub
<#1323 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF5MIDWX3BC2CKPLUALYYGLYYVMKJAVCNFSM6AAAAABEZQDJXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGM3TEMJXGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I turned on the Use HD Camera Resolutuon setting under the View menu and it's working now! |
|
Great - that's the other thing to try :) |
I'm now getting an EXC_BAD_ACCESS (SIGABRT), indicates a crash caused by a memory access violation in Sparrow when trying to read the camera for a Seed Signer import. This type of error often occurs when an application tries to read or write to memory that hasn't been allocated, or that has been deallocated. The specific address causing the problem is at 0x00000000000000b4, which suggests an attempt to access memory near the beginning of the address space, often indicative of a null pointer dereference or a similar issue.
The crash occurs in a thread named Java: atomic-processor-1.
The text was updated successfully, but these errors were encountered: