[BUG] UVtools 2.14.1 crashes on launch #236
Comments
|
I just went ahead and tested 2.14.0 to see if it had the same issue. It does not. It's only been a few minutes, but so far 2.14.0 seems to work as well as 2.13.4 did. I'm switching to 2.14.0 for now instead. Update: After using it for more than an hour I can confirm 2.14.0 works well, exports files that print, etc. |
|
2.14.1 upgraded opencv which introduced some new stuff that may not compatible with emulation, from the logs you sent i can't see it loaded so maybe is that. To access logs, go to UVtools -> Help -> Open settings folder. Is there a errors.log? I also can send a alternative libcvextern to you try replace the original and test |
|
Lets try this by multiple trys:
Try to run If fail try to:
If it fail try to:
|
|
I had exactly the same issue as OP with v2.14.1. |
|
My build v2.14.0 was compiled on Monjave x64 and v2.14.1 was compiled on Catalina x64... But my guess is something new on the opencv that is missing... It works under my VM but is x64... I have no way to compile nor test under M1 Try put the x64/libcvextern.dylib into UVtools/Contents/MacOS |
|
Tried the x64/libcvextern.dylib - no difference unfortunately, still crashes on opening! |
|
Ok i compile it under Monjave and send the libs to test out |
|
I also have the bigsur libs. |
|
Sorry, no luck! Tested with - from bigsur archive
|
|
ok, so did a bit of digging... The libcvextern in the 12.14.0 release is quite a bit smaller than the ones you've linked to above, so maybe it's much older? |
|
libcvextern.dylib: Is some dependency that changed on opencv452 that mac refuse to load or have in compability mode. While old library works with new uvtools, it can give problems on flip operations. It work fine on Catalina and bigsur x64 |
|
Just throwing it out there that I'm happy to test any native m1 version you experiment with - that might 100% fix the problem :) |
|
Native UVtools on M1 will require .NET 6.0: #187 |
|
Ah ok, that's a shame! I was going to offer to compile native m1 opencv4.5.2 for you, but guess that won't help at all if it needs .net v6 :/ |
|
Yeah, but will be welcome when i upgrade to .NET 6.0 |
|
Just tried your first set of solutions and got the same results as rfield19 (from the https://we.tl/t-mhVUQVBFFu) libraries, and decided it is a safe assumption I would get the same results on the second set (the Big Sur libraries at https://we.tl/t-gnRgLCiU8K -- please let me know if you'd like a second set of tests on those) so I haven't tried them yet. I did go ahead and try the copying libcvextern (only) from 2.14.0 to 2.14.1 as rfield19 said worked for them, and it worked for me as well. Would that lose any functionality? Also, although the Settings menu item in File works fine, "Open Settings Folder" in the Help menu does not seem to do anything. I hope that helps. |
Only if you start to play with Flip function... Other than that is safe |
|
Try this monjave build. Remove old things you put on uvtools before. |
|
No difference with new files unfortunately - doesn't load. |
|
with libusb included right? |
|
that was with libusb included also, yes. edit: actually I'm not even sure it would work inside a vm anyway - as parallels can only run arm versions of windows iirc. |
|
I mean, run terminal/console in Rosetta 2 Emulation Mode |
|
Perhaps an old version of iterm might run in rosetta2 mode - not sure. |
|
Lets try natively to see. Open a terminal on UVtools content folder, and try these commands: |
|
OK, I've downloaded an old version of iterm2 - v 3.3.1.2 and it seems to be running under rosetta2 (I've got an app called silicon info running in the taskbar that tells me what it's running as). If I type /Applications/UVtools.app/Contents/MacOS/libcvextern.dylib (architecture x86_64): |
|
and if I do error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/otool-classic: can't map file: /Applications/UVtools.app (Invalid argument) |
Yes, must be: otool -L /Applications/UVtools.app/Contents/MacOS/UVtools Can you run the otool on the working libcvextern.dylib (from previous version) |
|
OK, that's better! otool -L /Applications/UVtools.app/Contents/MacOS/UVtools /Applications/UVtools.app/Contents/MacOS/UVtools: on the default 2.14.1 app )no changes) I get otool -L /Applications/UVtools.app/Contents/MacOS/libcvextern.dylib On the 2.14.1 app but with the 2.14.0 libcvextern.dylib copied into it, I get: /Applications/UVtools.app/Contents/MacOS/libcvextern.dylib (architecture x86_64): |
|
Ok so the diffs are: https://www.diffchecker.com/aXry9pU7
Can you confirm if such blue highlight libraries exists on your mac? |
|
ok1ok1 - that's not the behaviour I'm seeing on an m1 mac. |
|
@rfield19 You are correct. I used a libcvextern file that was posted/recomended earlier in the thread. Replacement using the file from 2.14.0 did work. |
|
It looks like some features are broken when using the replacement libcvextern. Exposure finder for example returns a lot of errors and doesn't generate any slices. |
May be, old libcvextern use different Mirror/Flip enumeration. |
|
Try this dylib: https://we.tl/t-nYETPG5yeM |
|
I'm not sure what you mean by remove from folder. I did remove from brew using I replaced libvextern.dylib in the application package with the version you posted. |
Dam, it worked for me on x64. You on M1? |
|
@sn4k3 yeah, I'm using an M1. |
Ok, still not good for M1... |
|
@sn4k3 I can confirm on x64 - libusb removed from brew and as expected the 2.15.0 app doesn't load. |
Ok so thats a progress. Thanks for confirming |
|
Not sure if this is any help diagnosing it but; Tried the dylib from above too with no success |
|
I'm out, can't verify, but maybe is possible that i forget to update the dylib on the release, please try this: #236 (comment) |
The MD5 of both files are identical, so hence didn't fix it sadly :( |
|
It seems to be actually loaded if I move it to /usr/local/lib/libcvextern and remove the .dylib, then libpng breaks saying it couldn't be found where it's expected. Seeing if I can force it to work, but looks like in general the dylib is failing to be properly loaded. |
|
@shrimpyuk do you have an m1 cpu by any chance? @sn4k3 2.15.1 is working absolutely fine here on x64 mac, no file changes were necessary (and libusb is not installed in brew or elsewhere). |
|
@sn4k3 Yes, I saw that one. I'm on osx 11.4 rather than 11.5, but other than that everything should be the same. shrimpyuk did mention it saying it wasn't able to find libpng however - could the crash be related to that rather than libcvextern now? I do have libpng (as well as libjpg and libtiff) installed with brew from some other project ; it's in /usr/local/opt/libpng, and if I do an otool -L /Applications/UVtools.app/Contents/MacOS/libcvextern.dylib then I do see |
|
]
I'm on macOS 12.0 Beta, but don't think thats where the differences is, however I am on M1. I installed libpng manually however that didn't help as he binary was expecting a x64_86 version. Not sure why on earth this suddenly broke to be honest :( |
|
Okay, magically seemed to fix it by downloading 2.14.0 and splicing libcvextern into 2.15.1, M1 macOS 12.0 Beta |
|
@shrimpyuk yes if you're on m1 then that's why it's not working for you. On my m1 I'm therefore using 2.15.1 with libcvextern.dylib from 2.14.0 version as well as libusb via brew. It's not ideal (a few functions don't work), but mostly works ok. edit: just seen you've posted the same fix whilst I was typing! |
|
Please test the new release and report back. |
|
@sn4k3 I think you might have solved it! Oh, and flip function works fine too :) |
Perfect! Lets wait for more feedback :) |
|
2.16.0 ran on this older intel iMac |
|
Working well for me on M1 mac. |
|
Nice, seen to be fixed :) Closing now |
System
Describe the bug
I had been using UVtools 2.13.4 without issue for a while now, but was hoping for a feature that would allow me to delete layers at the bottom to remove islands just slightly above the build plate, so figured I would roll the dice and upgrade when I noticed that 2.14.1 was available today. I used the "automatic upgrade" feature, which seemed rather manual since it just opened the web page to download the new release, downloaded 2.14.1, replaced the old one, and opened it, and it crashed on open (never displayed a GUI - just an OS crash log). Tried it again, crashed again. Every single time. Right clicking to open changed nothing. I tried the old version, it still works fine. So I'm going back to the old version.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It does not crash and runs as normal
Screenshots
It's just your standard "Problem Report for Avalonia Application" for the title, and "Avalonia Application quit unexpectedly." below that, "Click Reopen to open the application again. This report will be sent to Apple automatically."
Really not worth a screenshot. There is a lot of info in the crash log, which would not be captured adequately in a screenshot in any case, which I'll paste below.
Files
Not Applicable.
Exceptions Log file
I'm not sure where this AppData folder would be, I didn't see it inside the UVtools application package folder or in my user/Library/Application Support folder (no UVtools folder there) or the system Application Support. I'm guessing it didn't get launched enough to write anything anyway, but I'd be interested to know where exactly that log gets written on a Mac, if someone knows.
However there is a large crash log as I mentioned above, generated by the OS. I'll put that in Additional Context since no one would want to try to scroll past it to read anything else.
Additional context
Here's that crash log:
The text was updated successfully, but these errors were encountered: