Crashing while opening dialog with attachments (#549)

Unknown opened 4 years ago

The bug appears unexpectedly when somebody from the conference sent an attachment (image or video -- I can't say for sure). After that happened, launching raises a crash every time.

Desktop:

OS: Mac OS 10.15.6
Browser: Chromium
Version: 83.0.4103.106

Additional context

Process:               BeagleIM [5972]
Path:                  /Applications/BeagleIM.app/Contents/MacOS/BeagleIM
Identifier:            org.tigase.messenger.BeagleIM
Version:               4.0 (103)
Code Type:             X86-64 (Native)
Parent Process:        bash [5966]
Responsible:           iTerm2 [1289]
User ID:               1278397356

Date/Time:             2020-10-19 23:30:13.941 +0300
OS Version:            Mac OS X 10.15.6 (19G73)
Report Version:        12
Bridge OS Version:     3.0 (14Y908)
Anonymous UUID:        351F2BF6-CE15-B302-BE3D-C8F8F87E73A9

Sleep/Wake UUID:       87946874-813F-4B45-8824-41DC45D5D719

Time Awake Since Boot: 4000000 seconds
Time Since Wake:       560 seconds

System Integrity Protection: enabled

Crashed Thread:        6  Dispatch queue: eventbus_queue 5E27599F-1473-4D09-9658-090E685963BE

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [5972]

Application Specific Information:
Fatal error: Duplicate values for key: 'razrab@***.***': file /Library/Caches/com.apple.xbs/Binaries/SwiftPrebuiltSDKModules_macOS/install/TempContent/Objects/EmbeddedProjects/CrossTrain_macOS_SDK/macOS_SDK/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/swift/Swift.swiftmodule/x86_64.swiftinterface, line 11105

Unknown commented 4 years ago

Could you attach a full crash log? Partial log is not really helpful and cannot be used to replicate or solve the issue.

Unknown commented 4 years ago

Sure. For the full log see report.txt.

Unknown commented 4 years ago

I've added a fix (or rather a workaround) as in a <message/> stanza which you received you had multiple stable ids provided with the same by attribute. That is something which should not happen but I've protected BeagleIM against crashing in this case.

Unknown commented 4 years ago

Amazing! The latest beta is not crashing now! ??

	Unknown opened 4 years ago The bug appears unexpectedly when somebody from the conference sent an attachment (image or video -- I can't say for sure). After that happened, launching raises a crash every time. Desktop: OS: Mac OS 10.15.6 Browser: Chromium Version: 83.0.4103.106 Additional context Process: BeagleIM [5972] Path: /Applications/BeagleIM.app/Contents/MacOS/BeagleIM Identifier: org.tigase.messenger.BeagleIM Version: 4.0 (103) Code Type: X86-64 (Native) Parent Process: bash [5966] Responsible: iTerm2 [1289] User ID: 1278397356 Date/Time: 2020-10-19 23:30:13.941 +0300 OS Version: Mac OS X 10.15.6 (19G73) Report Version: 12 Bridge OS Version: 3.0 (14Y908) Anonymous UUID: 351F2BF6-CE15-B302-BE3D-C8F8F87E73A9 Sleep/Wake UUID: 87946874-813F-4B45-8824-41DC45D5D719 Time Awake Since Boot: 4000000 seconds Time Since Wake: 560 seconds System Integrity Protection: enabled Crashed Thread: 6 Dispatch queue: eventbus_queue 5E27599F-1473-4D09-9658-090E685963BE Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Illegal instruction: 4 Termination Reason: Namespace SIGNAL, Code 0x4 Terminating Process: exc handler [5972] Application Specific Information: Fatal error: Duplicate values for key: 'razrab@*.*': file /Library/Caches/com.apple.xbs/Binaries/SwiftPrebuiltSDKModules_macOS/install/TempContent/Objects/EmbeddedProjects/CrossTrain_macOS_SDK/macOS_SDK/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/swift/Swift.swiftmodule/x86_64.swiftinterface, line 11105
	Unknown commented 4 years ago Could you attach a full crash log? Partial log is not really helpful and cannot be used to replicate or solve the issue.
	Unknown commented 4 years ago Sure. For the full log see report.txt.
	Unknown commented 4 years ago I've added a fix (or rather a workaround) as in a `<message/>` stanza which you received you had multiple stable ids provided with the same `by` attribute. That is something which should not happen but I've protected BeagleIM against crashing in this case.
	Unknown commented 4 years ago Amazing! The latest beta is not crashing now! ??